Gateway interface for an enhanced circuit breaker disconnect

ABSTRACT

A system includes a solid-state circuit breaker coupling between a power supply and an electrical load. The system also includes a gateway interface device communicatively coupled to the solid-state circuit breaker and includes a plurality of communication interfaces. In an embodiment, the gateway interface device includes a controller configured to perform operations including determining a connection status of at least one communication interface of the plurality of communication interfaces and determining a number of devices connected to the at least one communication interface, receive a signal from at least one device of the number of devices. In the embodiment, the operations may also include in response to receiving the signal, instructing the solid-state circuit breaker to disconnect the electrical load from the power supply.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 17/035,631, filed Sep. 28, 2020, and entitled “Gateway Interface for an Enhanced Circuit Breaker Disconnect,” which is a continuation-in-part of U.S. application Ser. No. 16/797,817, filed Feb. 21, 2020, and entitled “Motor Control Center with Enhanced Circuit Disconnect”, each of which is herein incorporated by reference in its entirety and for all purposes.

BACKGROUND

This disclosure relates generally to systems and methods for circuit breakers used within industrial automation systems. More specifically, the present disclosure discusses a solid-state circuit breaker, which may be used to protect a portion of an industrial automation system.

This section is intended to introduce the reader to various aspects of art that may be related to various aspects of the present techniques, which are described and/or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present disclosure. Accordingly, it should be understood that these statements are to be read in this light, and not as admissions of prior art.

An industrial automation system may include a variety of components associated with different types of motors and motor-drive configurations. For example, different motor-drive configurations may use different types of protection and electrical isolation systems to protect various electrical components connected to a motor-drive system from certain overvoltage and/or overcurrent situations. To effectively protect and operate a variety of types of motors and electrical systems in an industrial automation system, circuit breakers may be included between an electrical load (e.g., a motor) and a power supply.

SUMMARY

A summary of certain embodiments disclosed herein is set forth below. It should be understood that these aspects are presented merely to provide the reader with a brief summary of these certain embodiments and that these aspects are not intended to limit the scope of this present disclosure. Indeed, this present disclosure may encompass a variety of aspects that may not be set forth below.

In one embodiment, a system may include a solid-state circuit breaker configured to couple between a power supply and an electrical load and a gateway interface device communicatively coupled to a controller of the solid-state circuit breaker. The controller may include a plurality of communication interfaces, wherein each of the plurality of communication interfaces is configured to communicate using a different communication protocol. The controller is configured to perform operations including determining a connection status of at least one communication interface of the plurality of communication interfaces based on a set of data signals received via the at least one communication interface and determining a set of devices connected to the at least one communication interface based on the set of data signals received via the at least one communication interface. The controller is also configured to perform operations including generating a node list associated with each device of the set of devices, wherein the node list is representative of one or more devices communicatively coupled to the controller via the at least one communication interface and creating a data table configured to map data received from each device of the set of devices into a shared memory based on the node list. The controller is also configured to perform operations including storing a set of data from the set of devices in the shared memory based on the data table.

In another embodiment, a method may include determining, by a processor, an operational status of a solid-state circuit breaker disposed in an enclosure and in response to the operational status indicating that the solid-state circuit breaker is coupling a voltage source to an electrical load: determining, by the processor, a door position status for a door of the enclosure, wherein the door is associated with the solid-state circuit breaker; determining, by the processor, a lock position status for a lock associated with the door; and adjusting, by the processor, an operational status of the solid-state circuit breaker based on the door position status, the lock position status, or a combination thereof.

In yet another embodiment, a system includes a plurality of solid-state circuit breakers, each solid-state circuit breaker configured to couple between a power supply and an electrical load and a gateway interface device communicatively coupled to the plurality of solid-state circuit breakers. The gateway interface device includes a plurality of communication interfaces and a controller configured to perform operations comprising: identifying a portion of the plurality of solid-state circuit breakers for one or more load shedding operations based on a set of operational statuses for the portion of the plurality of solid-state circuit breakers; determining a total electrical load associated with the plurality of solid-state circuit breakers exceeds a threshold; and causing the portion of the plurality of solid-state circuit breakers to open in response to the total electrical load exceeding the threshold.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features, aspects, and advantages of the present disclosure will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:

FIG. 1 is a block diagram of a load-feeder system protected by a solid-state circuit breaker, in accordance with an embodiment;

FIG. 2 is a block diagram of a motor-feeder system protected by the solid-state circuit breaker of FIG. 1 , in accordance with an embodiment;

FIG. 3 is a block diagram of non-motor-feeder system protected by direct current (DC) solid-state circuit breaker, in accordance with an embodiment; and

FIG. 4 is a method for operating the solid-state circuit breaker of FIG. 1 as part of a soft-start operation, in accordance with an embodiment;

FIG. 5 is a block diagram of a first starter system and a second starter system that uses the solid-state circuit breaker of FIG. 1 to control a motor, in accordance with an embodiment;

FIG. 6 is a block diagram of a first reversing starter system and a second reversing starter system that uses the solid-state circuit breaker of FIG. 1 to control a motor, in accordance with an embodiment;

FIG. 7 is an illustration of a housing unit for the solid-state circuit breaker of FIG. 1 , in accordance with an embodiment;

FIG. 8 is an illustration of a cabinet that includes the housing unit of FIG. 7 and the solid-state circuit breaker of FIG. 1 , in accordance with an embodiment;

FIG. 9 is an illustration of the housing unit of FIG. 7 and the solid-state circuit breaker of FIG. 1 , in accordance with an embodiment;

FIG. 10 is an illustration of an enclosure that includes the housing unit of FIG. 7 and the solid-state circuit breaker of FIG. 1 , in accordance with an embodiment;

FIG. 11 is a block diagram of a motor-feeder system protected by the solid-state circuit breaker of FIG. 1 incorporating a gateway interface device, in accordance with an embodiment;

FIG. 12 is a block diagram of the gateway interface device of FIG. 11 , in accordance with an embodiment;

FIG. 13 is a block diagram of the gateway interface device of FIG. 11 incorporating digital signal interfaces, in accordance with an embodiment;

FIG. 14 is a flow chart of a method for determining device connections for the gateway interface device of FIG. 11 , in accordance with an embodiment;

FIG. 15 is a flow chart of a method for communicating between connected devices and the solid-state circuit breaker of FIG. 1 using the gateway interface device of FIG. 11 , in accordance with an embodiment;

FIG. 16 is a flow chart of a method for operating the housing unit of FIG. 7 using the gateway interface device of FIG. 11 prior to energizing the solid-state circuit breaker of FIG. 1 , in accordance with an embodiment;

FIG. 17 is a flow chart of a method for operating the solid-state circuit breaker of FIG. 1 using the gateway interface device of FIG. 11 in response to a status of the housing unit of FIG. 7 , in accordance with an embodiment;

FIG. 18 is a flow chart of a method for controlling operation of a set of circuit breakers using the gateway interface device of FIG. 11 , in accordance with an embodiment; and

FIG. 19 is a flow chart of a block diagram of the gateway interface device of FIG. 11 incorporating a Universal Serial Bus (USB) interface, in accordance with an embodiment.

DETAILED DESCRIPTION

One or more specific embodiments of the present disclosure will be described below. In an effort to provide a concise description of these embodiments, all features of an actual implementation may not be described in the specification. It should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another. Moreover, it should be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this present disclosure.

When introducing elements of various embodiments of the present disclosure, the articles “a,” “an,” “the,” and “said” are intended to mean that there are one or more of the elements. The terms “comprising,” “including,” and “having” are intended to be inclusive and mean that there may be additional elements other than the listed elements.

The present disclosure is generally directed toward techniques for improving operation of an industrial automation system, and specifically to improving protective circuitry used to protect an electrical load from undesired operating conditions, such as an overvoltage and/or an overcurrent operating condition. Technological advances in integrated circuit technology have enabled solid-state circuitries, such as carbon nanotubes and/or silicon-carbide-based circuitry (SiC-based circuitry), to replace other semiconductor devices within an industrial automation system. Indeed, barriers to using SiC semiconductors have included commercial price and volatility of materials used to form SiC semiconductors, conduction losses associated with driving SiC semiconductors, and heat dissipation challenges associated with driving SiC semiconductors. Furthermore, some SiC semiconductors have conduction losses and heat dissipation challenges that may make devices formed from SiC semiconductors inefficient. Nevertheless, by employing the SiC semiconductors to perform the operations described herein, the benefits achieved in various industrial application may outweigh the drawbacks that are attributed to the barriers discussed above.

In general, protective circuitry built from SiC semiconductor devices may be capable of operating at higher temperatures and/or higher currents relative to traditional systems that do not use SiC semiconductor devices. Semiconductor devices have proved to be challenging to incorporate into circuitries described below due to properties such as, limited thermal conductivity, limited switching frequencies, a relatively low band gap energy, and high-power losses. Thus, protective circuitry, such as circuit breakers, have avoided the use of solid-state circuitry in favor of other protective devices, such as mechanical circuit breakers, fuses, and the like. Devices that use silicon carbide (SiC) semiconductor devices (e.g., SiC insulated-gate bipolar transistors (IGBT), SiC metal-oxide semiconductor field-effect transistor (MOSFET), or other suitable transistor), however, may have relatively improved performance when compared to other types or protective circuitries. For example, protective circuitry that uses a SiC semiconductor device may be capable of withstanding higher voltages (e.g., 10× higher) than other semiconductor devices. This feature may allow the SiC semiconductor to be employed as protection circuitry, as described in more detail below, for industrial applications, which operation in medium to high voltage ranges. Moreover, SiC semiconductor devices may operate under higher ambient temperature conditions, as compared to other semiconductor devices, thereby enabling the SiC semiconductor devices to maintain its reliability while operating in industrial environments.

In addition, as will be detailed below, the protection circuitry used in various industrial applications rely on multiple components to perform distinct functions. Each of these components are incorporated into the design of enclosures used to house the components. As a result, the housing may become larger as more protection circuit components are used to protect various parts of the industrial system. By performing the embodiments described herein, the functionalities of these separate components may be integrated into the SiC semiconductor devices to reduce the form factor or size of the enclosures previously used to house the protection circuit components. The reduced size attributes for the various types of protection circuitries may enable the industrial automation systems to perform in more confined areas. Moreover, although the costs associated with the SiC semiconductor devices may continue to deter use of SiC semiconductor devices in certain industrial applications, by employing the embodiments described herein, the SiC semiconductor devices may be used to efficiently replace a number of components to allow operations to be controlled in a more effective manner in a limited amount of space.

An example protective device that includes SiC semiconductor devices may be a solid-state circuit breaker. Solid-state circuit breakers may provide the particular advantage of not using mechanical switching to open or close a circuit. Reducing or eliminating use of mechanical switching may reduce a likelihood of arc flash and/or reduce a severity of exposed incident energy if an arc flash were to occur. When occurrences of arc flash are reduced, reliability and lifespans of systems using solid-state circuit breakers may improve (e.g., increase). Furthermore, since a likelihood of arc flash may be eliminated and/or reduced when using a solid-state circuit breaker, operators of solid-state circuit breakers may reduce a level of personal protective equipment (PPE) worn while operating the solid-state circuit breakers, such as the level of PPE worn when restarting (e.g., coupling line-side (or supply-side) to load-side, coupling supply-side to load-side) a solid-state circuit breaker after a trip event of the solid-state circuit breaker. This may also apply to levels of PPE worn when working around or nearby to equipment protected by the solid-state circuit breaker (e.g., equipment downstream from the solid-state circuit breaker).

Keeping the foregoing in mind, motor control centers (MCCs) may be designed to use solid-state circuit breakers compatible with three-phase (e.g., multi-phase) electrical distribution systems. The solid-state circuit breakers may be used as an independent electrical feeder (e.g., main line) and/or as a motor starter, in combination with additional solid-state circuit breakers as a motor starter, and/or in similar operation as a non-solid-state circuit breaker. As such, the solid-state circuit breaker may be suitable for protection of electrical couplings between a power source or supply for a motor and the motor (e.g., feeder between a generator and a motor as depicted in FIG. 1 ), as well as for protection of electrical couplings between an inverter and a motor (e.g., as overload protection circuitry depicted in FIG. 2 ). When using the solid-state circuit breaker as a motor starter, the solid-state circuit breaker may be operated to perform a reverse starting operation, a non-reverse (e.g., forward) starting operation, a soft-start starting operation (e.g., stepped starting operation), and the like.

By definition, a starter that does not implement SiC semiconductor technologies may include three major components: a galvanic disconnecting device with branch circuit protection (e.g., a circuit breaker, fused disconnect switch), a thermal overload protection device (e.g., electronic overload), and an isolating device in the form of a contactor. These three components work together as a starter assembly for a motor load (e.g., electric motor circuit), such as a full voltage non-reversing starter system. For example, each disconnect switch in a starter may operate at a same time to open or close the electrical circuit to the motor load.

In another embodiment of a starter, such as a full voltage reversing starter, a second contactor may be added to a circuit of the starter in parallel with a first contactor, providing an electrical phase reversal of two phases feeding the starter (e.g., line 1 (L1), line 3 (L3)). By interlocking these contactors and swapping phases, one contactor may be engaged in the “on” position at a given time. As the second contactor has two electrical phases swapped, the electrical phase rotation is 180 degrees different from the first contactor and may drive a motor in the reverse direction.

In the industrial automation system, the starter described above (e.g., full voltage non-reversing starter) may be replaced by a starter that uses SiC semiconductors to improve operation of the starter without SiC semiconductors. For example, the electronic overload device and isolation switch between line-side (e.g., supply-side) and load-side of the above-referenced starter (e.g. contactor functionality) may be embedded within a solid-state circuit breaker as a single component. These components, embedded into a single solid-state circuit breaker, may eliminate the contactor and overload components.

By applying a similar manufacturing principle to the full voltage reversing starter, a new starter may be formed by including SiC semiconductor devices additionally or alternatively to non-SiC devices. For example, the electronic overload device and isolation switches (e.g. contactors) may be embedded within a solid-state circuit breaker, and the solid-state circuit breaker may use firmware to provide similar or equivalent phase reversal capabilities as the electronic overload device and/or isolation switches. These components, as embedded into a single solid-state circuit breaker, eliminate the contactors and overload components.

In these discussed examples of full voltage starters (e.g., reversing, non-reversing), branch circuit protection is provided as a function of the solid-state circuit breaker itself. The solid-state circuit breaker may also operate to interrupt its circuit aligned with (e.g., at a suitable frequency, at a suitable response time) various standards of electrical governing bodies. Similarly, the solid-state circuit breaker may also operate in response to detection of a short circuit with a response time and/or response behavior in accordance with the standards of electrical governing bodies.

Some solid-state circuit breakers may include an integrated air-gap disconnect. The integrated air-gap disconnect may permit galvanic isolation between line-side and load-side within the solid-state circuit breaker as opposed to in line with the solid-state circuit breaker. Control circuitry of the solid-state circuit breaker may utilize the integrated air-gap disconnect to perform lockout/tagout control operations. The galvanic isolation protection provided within the solid-state circuit breaker may be further supplemented by including an additional circuit breaker and/or fused disconnect switch upstream of the solid-state circuit breaker, such as to further decouple the solid-state circuit breaker from a portion of a circuit. In some cases, the solid-state circuit breaker may be associated with a latch mechanism that interlocks the solid-state circuit breaker. Interlocking the solid-state circuit breaker may stop an operator from removing the solid-state circuit breaker while the solid-state circuit breaker is closed.

In some cases, a mechanical device may be included within the solid-state circuit breaker to operate a galvanic disconnecting device within the solid-state circuit breaker additional to or alternative of the latch mechanism and/or the fused disconnect switch. Operating the galvanic disconnecting device into an open position (e.g., such that an air gap is present between metal contacts associated with a line-side and a load-side of the solid-state circuit breaker) may provide mechanical galvanic isolation. It is noted that in some cases the galvanic disconnecting device implements or is the integrated air-gap disconnect. The mechanical device may be installed and attached to a physical disconnect handle that extends to the outside of a motor control center unit or drawer. Operating the physical disconnect handle to cause the mechanical device to operate the galvanic disconnecting device may provide a way to physically decouple a supply-side from a load-side of the solid-state circuit breaker. Physically decoupling the supply-side from the load-side of the solid-state circuit breaker may reduce a likelihood of arcs occurring during the removal of the solid-state circuit breaker and/or may be desired in certain maintenance operations and/or for unit withdrawal, such as to comply with the various electrical governing bodies standards and/or when additional isolation of the solid-state circuit breaker from an electrical supply is desired.

By keeping the foregoing in mind, the solid-state circuit breaker may perform operations of overload protection circuitry, disconnect switching circuitry, and motor controlling circuitry using circuitry within a same physical enclosure, such as when performing starting or steady state operations. This may permit the three devices (e.g., overload protection circuitry, disconnect switching circuitry, and motor controlling circuitry) to be replaced by the solid-state circuit breaker within a starter.

Furthermore, it should be noted that the solid-state circuit breaker may generate relatively large amounts of heat during switching operations since semiconductor materials generally increase in temperature during operation. To combat increases in operating temperatures, a thermal management system may be installed within the motor control center assembly to dissipate and remove heat from the solid-state circuit breaker and/or from air surrounding the solid-state circuit breaker. The thermal management system may create a bonded connection to each solid-state circuit breaker unit or drawer, thereby providing a path from the bonded connection to dissipate thermal energy. For example, the bonded connection and/or path may cause heat to dissipate through a passive heat sink formed from aluminum or other suitable conductive material and/or a heat sink that passively and/or actively involves conduction, such as using ambient air and/or forced air (e.g., cooling air) to keep equipment at a suitable temperature. In some cases, the physical thermal connection between the single component starter and thermal management system may be a heat pipe design that passively and/or actively involves conduction, such as using ambient air and/or forced air (e.g., cooling air) to keep equipment at a suitable temperature.

In some cases, a solid-state breaker may also be operated as part of a selective coordination schemes. For example, a group of solid-state breakers may be logically grouped to protect one or more electrical loads. Two or more protection devices configurable to monitor and protect against overcurrent and/or overvoltage conditions in tandem may be said to be selectively coordinated (e.g., operated in accordance with and/or using selective coordination schemes). As such, two or more selectively coordinated solid-state circuit breakers may work together to protect an electrical load from a fault (or otherwise undesired operation) by opening the downstream solid-state circuit breakers relative to the fault before the upstream solid-state circuit breakers responds to the fault (e.g., by opening).

Furthermore, in some embodiments, a solid-state circuit breaker may include a controller area network (CAN) communicative coupling (e.g., CANBUS®) and/or an internet protocol (IP)-based communicative coupling, such as an Ethernet IP communicative coupling and/or Ethernet internet protocol (IP), to a control system. These communicative couplings may enable the solid-state circuit breaker to directly communicate with the control system (e.g., a microcontroller) without a host computer. The communicative couplings between the solid-state circuit breaker and the control system may be used with a configuration interface. The configuration interface may be a user interface and/or logically-defined data object (e.g., data table) that permits a control system and/or user to provide and/or update a configuration and/or obtain a status of the solid-state circuit breaker. In this way, the configuration interface may be a data boundary used to translate configurations from devices external to the solid-state circuit breaker to a format readable by the solid-state circuit breaker and/or to translate statuses from the solid-state circuit breaker into a format readable by devices external to the solid-state circuit breaker. Indeed, a graphical user interface managed by the control system may enable a user to enter or adjust configurations of the solid-state circuit breaker by changing information stored in the configuration interface.

In some embodiments, the configuration interface may perform a format translation of data associated with it, such as to change a data type or length. The configuration interface may be embedded within computer-readable medium and executed as software to provide a single point of entry to a configuration of the solid-state circuit breaker. It is from the configuration interface that configuration of the solid-state circuit breaker may be dynamically updated in real-time to more suitably operate in a present process and/or present power condition of the industrial automation system.

Node addresses, protection settings (e.g., analog settings, discrete settings), or the like may each be set, reset, and/or defined via data stored in the configuration interface. The configuration interface may also serve as a table of parameters to store configurations in an offline place for download when a replacement of a solid-state circuit breaker were to occur. This may improve start-up or replacement operations of the industrial automation system by reducing downtime associated with a replacement or maintain operation of the solid-state circuit breaker (e.g., since the configuration is relatively easy to download and upload into a device replacement for the solid-state circuit breaker). Additionally or alternatively, the configuration interface may store the requested packet interval from the solid-state circuit breaker to the control system, or vice-versa.

The control system may use the configuration interface to individually monitor and/or control the solid-state circuit breaker even while connected to other circuit breakers and/or devices. The configuration interface may facilitate in the control system providing a dynamic user interface on a graphical user interface that may enable an operator to configure properties of the solid-state circuit breaker. In some cases, different operators may have different levels of authentication that permit the different operators varying control and/or access levels to the operation of the solid-state circuit breaker, where the levels of authentication may be defined by a permission parameter associated with an operator profile for the operator. Indeed, some operator profiles (e.g., user profiles) may have different levels of access to information associated with operation of the solid-state circuit breaker (e.g., information accessible via a configuration interface).

The solid-state circuit breaker may communicate with the control system and/or other industrial automation control devices (e.g., computing devices, solid-state circuit breakers) using any suitable communication or programming technique. For example, additional devices may interface with the solid-state circuit breaker using direct programming techniques and/or supporting programming languages, such as structured text, ladder logic, sequential function chart, functional block programming, or the like. Real-time information may be exchanged between the solid-state circuit breaker and other devices, such as the control system. One of the solid-state circuit breaker and/or the control system may initiate the communication, and at the request for communication instruct the device with a requested packet interval. Communication between the solid-state circuit breaker and the control system may occur at the requested packet interval and cause a populating of a data table of the control system.

The control system may receive information from the solid-state circuit breaker in the form of logical tags. These logical tags may be used in process automation control strategies. The information from the solid-state circuit breaker may be extracted in an operator-defined data type (e.g., P_SolidStateBreaker) that may encapsulate real-time data from the solid-state circuit breaker in an object-oriented model. The solid-state circuit breaker may be represented by one or more visualizations of the object-orientated model, and thus any displayed statuses of the solid-state circuit breaker may change in real-time as data transmits to the control system from the solid-state circuit breaker. A human-machine interface presented on a display of a computing device may present the object-orientated model. Furthermore, the logical tags and information from the solid-state circuit breaker may populate computing applications to create a logical model of an MCC itself. Additional details with regard to the solid-state circuit breaker described above will be discussed below with reference to FIGS. 1-10 .

By way of introduction, FIG. 1 is a block diagram of a feeder system 10 (e.g., motor feeder system, motor control center (MCC) feeder system), which may be part of an industrial automation system. The feeder system 10 may include a power supply, such as an alternating current (AC) power supply 12, to supply power to loads coupled downstream. The feeder system 10 may also include a solid-state circuit breaker 14 coupled to the AC power supply 12. The AC power supply 12 may supply current and/or voltage to an electrical load 16 coupled to the solid-state circuit breaker 14.

When abnormal operation occurs, such as when a voltage that is uncharacteristically high or low is delivered to the electrical load 16, the solid-state circuit breaker 14 may electronically disconnect the AC power supply 12 from the electrical load 16. As such, the solid-state circuit breaker 14 may protect the electrical load from supply voltages and/or supply currents that may damage the solid-state circuit breaker 14.

Any suitable number of supply devices may be represented by the AC power supply 12, such as any combination of rectifiers, converters, power banks, generation devices, or the like. It should be understood that the feeder system 10 may include one or more motor-drive systems, motors, MCCs, or the like as the electrical load, or coupled between any of the depicted devices and that the feeder system 10 may include one or more additional components not depicted in FIG. 1 .

For example, the feeder system 10 may include any suitable type of rectifier device that includes a number of switches controllable by any suitable power converter. For example, the AC power supply 12 may include an active front end (AFE) converter, a diode converter, a thyristor converter, a diode front end rectifier, or the like. In some embodiments, the switches of the AC power supply 12 may be semiconductor-controlled devices, transistor-based (e.g., insulated-gate bipolar transistor (IGBT), metal-oxide semiconductor field-effect transistor (MOSFET), or other suitable transistor) devices, or other suitable devices in which the opening and/or closing of the switch may be controlled using an external signal (e.g., gate signal), which may be provided by the control system 18. The AC power supply 12 may provide AC supply signals (e.g., AC voltage, AC current, a regulated AC output) on a bus 20, which may be provided to the solid-state circuit breaker 14.

It is noted that the feeder system 10 may be used in a variety of industrial automation systems, such as food manufacturing, industrial operations systems, refineries, or the like. In this way, implementation and use of the solid-state circuit breaker 14 to protect various electrical loads may improve operations of industrial automation systems. For example, using a solid-state circuit breaker 14 may reduce or eliminate usage of electrical protection devices that rely at least partially on mechanical switching. Reducing or eliminating use of mechanical switching may reduce a likelihood of arc flash and/or reduce a severity of exposed incident energy if an arc flash were to occur. When occurrences of arc flash are reduced, reliability and lifespans of systems using solid-state circuit breakers 14 may improve (e.g., increase) and operators may reduce a level of personal protective equipment (PPE) worn while operating nearby to the solid-state circuit breaker 14.

Industrial automation systems may operate in response to signals generated by the control system 18. The control system 18 may include any suitable number of electronic devices and/or components to generate and/or manage generation of the control signals. For example, the control system 18 may include a communication component 22, a processor 24, a memory 26, storage 28, and input/output (I/O) ports 29, or the like, for generating and managing generation of control signals.

The communication component 22 may be a wireless or wired communication component that facilitates communication between the control system 18, the solid-state circuit breaker 14, or other suitable electronic devices. The processor 24 may be any type of computer processor or microprocessor capable of executing computer-executable code. The memory 26 and the storage 28 may be any suitable articles of manufacture that may serve as media to store processor-executable code, data, or the like. These articles of manufacture may represent computer-readable media (i.e., any suitable form of memory or storage) that may store the processor-executable code used by the processor 24 to perform the presently disclosed techniques, such as to predictively response to operational changes, or the like.

The I/O ports 29 may couple to one or more sensors, one or more input devices, one or more displays, or the like, to facilitate human or machine interaction with the control system 18, the solid-state circuit breaker 14, or other suitable electronic devices. For example, based on a notification provided to the operator via a display, the operator may use an input device to instruct the adjustment of a parameter associated with the solid-state circuit breaker 14.

Keeping the foregoing in mind, sometimes the control system 18 may communicate with the solid-state circuit breaker 14 using one or more communication techniques. For example, the solid-state circuit breaker 14 may include a controller area network (CAN) communicative coupling and/or an internet protocol (IP)-based communicative coupling, such as an Ethernet IP communicative coupling, to the control system 18. These communicative couplings may enable the solid-state circuit breaker 14 to communicate with the control system 18 without intervention from a host computer. Thus, the solid-state circuit breaker 14 may communicate directly with the control system 18 without using an intervening computing device.

In some cases, the control system 18 may use one or more configuration interfaces to communicate with the solid-state circuit breaker 14. The configuration interface may be a graphical user interface and/or logically-defined data object (e.g., data table) that permits the control system 18 and/or user to provide and/or update a configuration and/or to obtain a status of the solid-state circuit breaker. In this way, the configuration interface may be a data boundary used to translate configurations from devices external to the solid-state circuit breaker 14 to a format readable by the solid-state circuit breaker 14 and/or to translate statuses from the solid-state circuit breaker 14 into a format readable by devices external to the solid-state circuit breaker 14.

In some embodiments, the configuration interface may perform a format translation of data associated with it, such as to change a data type or length. For example, the configuration interface may facilitate changing an analog-defined parameter (e.g., data value, status) into a digitally-defined parameter, a Boolean-defined parameter into a Floating-point-defined parameter, from a character-defined parameter into a string-defined parameter, from an integer-defined parameter into a Boolean-defined parameter, or any combination thereof. The configuration interface may be embedded within computer-readable medium and executed as software to provide a single point of entry to a configuration of the solid-state circuit breaker. It is from the configuration interface that configuration of the solid-state circuit breaker may be dynamically updated in real-time to more suitably operate in a present process and/or present power condition of the industrial automation system.

A configuration interface may be associated with a table, or other type of data storage and/or data object, used to store parameters, information, identifiers, set-points, or the like. To communicate with the solid-state circuit breaker 14, the control system 18 may reference an identifier stored in a table associated with the communication interface and use the identifier to prefix a message and/or data packet to the solid-state circuit breaker 14 (e.g., a control system of the solid-state circuit breaker 14). The control system 18 may store information received from the solid-state circuit breaker 14 into the table (e.g., a current indication of data from a sensing operation), or the like, to associate the information with the configuration of the solid-state circuit breaker 14. The control system 18 may also use the configuration interface for a variety of suitable operations related to control and/or communication with the solid-state circuit breaker 14. For example, the control system 18 may determine, from the configuration interface, a first expected value range (e.g., a first data value and a second data value) associated with a first operation of the solid-state circuit breaker 14. In this way, the control system 18 may identify an undesired operation if a received sensed value was determined to not be between the first data value and the second data value (e.g., greater than or less than the expected value range).

Usage of the configuration interface may permit the control system 18 to individually monitor and/or control the solid-state circuit breaker 14 even while connected to other circuit breakers and/or devices. For example, the configuration interface may provide a direct communicative coupling from the control system 18 to the solid-state circuit breaker 14, even when a communicative coupling is shared between multiple solid-state circuit breakers 14, such as by routing communications and/or commands directly between the control system 18 and the solid-state circuit breaker 14. The configuration interface may permit configuration of properties of the solid-state circuit breaker 14 while the solid-state circuit breaker 14 is online. These properties may include an IP Address assigned to the solid-state circuit breaker 14 to permit communication between the control system 18 and the solid-state circuit breaker 14 and/or a node address (e.g., CAN node address) to permit the control system 18 to address the solid-state circuit breaker 14 as one of many nodes. Additionally or alternatively, the configuration interface may store the requested packet interval from the solid-state circuit breaker 14 to the control system 18, or vice-versa, where the requested packet interval may be a data transfer rate and/or data transmission frequency rate specified by a first device for a second to comply with when sending information or data to the first device.

In this way, the control system 18 may use configuration interface-based communication techniques to identify an IP address and/or the node address of the solid-state circuit breaker 14 to communicate with the solid-state circuit breaker 14 according to the requested packet interval. Knowing the IP address and/or node address of the solid-state circuit breaker 14 may permit a direct routing of information and/or commands to the solid-state circuit breaker 14.

The configuration interface may also serve as a table of parameters to store configurations in an offline place for download when a replacement of a solid-state circuit breaker 14 were to occur. This may improve start-up or replacement operations of the industrial automation system by reducing downtime associated with a replacement or maintain operation of the solid-state circuit breaker 14 (e.g., since the configuration is relatively easy to download and upload into a device replacement for the solid-state circuit breaker 14).

In some cases, the control system 18 may use the configuration interface-based communication techniques to instruct the solid-state circuit breaker 14 into a particular mode of operation. The mode of operation may define how signals are transmitted through or from the solid-state circuit breaker 14. For example, the solid-state circuit breaker 14 may be instructed into a soft-start operational mode, a forward operational mode, and/or a reverse operational mode, and thus may behave like a motor starter. In some cases, the solid-state circuit breaker 14 may be operated in combination with one or more additional solid-state circuit breakers 14 also operated into the same operational mode. The soft-start operational mode may cause the solid-state circuit breaker 14 to provide incrementally-generated supply power or supply signals to the electrical load 16, such as to provide a start-up level of supply signals at a relatively gradual pacing or timing. The forward operational mode may cause the solid-state circuit breaker 14 to provide supply power in a way to cause the electrical load to operate in a forward direction relative to a reference direction, while the reverse operational mode may cause the solid-state circuit breaker 14 to provide supply power in a way as to cause the electrical load to operate in a reverse direction relative to the reference direction.

The control system 18 may also permit configuration of properties of the solid-state circuit breaker 14 based at least in part on thermal measurements and/or metering information, such as phase-phase voltages, phase-to-ground voltages, input current, output current, frequency, power, status of the solid-state circuit breaker 14 (e.g., Open Close, Blocked, Failure), or the like. In this way, the control system 18 may determine a current operation of the solid-state circuit breaker 14 and use the information of the current operation to determine how to adjust an operation of the solid-state circuit breaker 14. For example, the control system 18 may determine that the solid-state circuit breaker 14 is blocked and has a thermal measurement higher than a historical average for the solid-state circuit breaker 14. Using this information, the control system 18 may determine that an undesired operation is occurring, and thus may determine to open the solid-state circuit breaker 14. Furthermore, the control system 18 may use this information to operation other devices upstream and/or downstream of the solid-state circuit breaker 14, such as controlling additional protection circuitry to further isolate the solid-state circuit breaker 14 from the industrial automation system.

The properties, in some embodiments, may also be used to define operation limits corresponding to determined settings to be used to protect the load. The operation limits may correspond to operating ranges set by governing agencies or standard committees, such as American National Standards Institute (ANSI®), Underwriters Laboratories (UL®), International Electrotechnical Commission (IEC®) or the like, and may be used to protect the solid-state circuit breaker 14, the electrical load 16, or the like from undesired operating conditions. Furthermore, the properties may also define protection groups or classes associated with the solid-state circuit breaker 14. Protection groups or classes may correspond to groups of electrical loads 16 that may have a same protection scheme. These protection groups or classes may be classifications of types of protection for different devices set by governing agencies or standard committees. When the electrical load 16 is classified as part of a protection group with another electrical load 16, it may be desired to protect both electrical loads 16 with a solid-state circuit breaker 14 set to the same settings. In this way, when a different electrical load 16 is installed to the solid-state circuit breaker 14, the protection groups or classes may be updated to indicate the new group or class of the new electrical load 16. This may cause the solid-state circuit breaker 14 to automatically update its operational settings to accommodate the new electrical load 16. Use of properties may thus improve deployment of setting changes to solid-state circuit breakers 14 by making an overall installation process of a new electrical load 16 relatively faster since less time is spent updating operational settings of the solid-state circuit breaker 14. In some embodiments, the solid-state circuit breaker 14 may detect a protection group or class of its electrical load 16 automatically and/or without receiving the property from the control system 18. In these cases, the solid-state circuit breaker 14 may sense metering information (e.g., operational properties) of the electrical load 16 to determine what protection group or class applies to the electrical load 16. For example, the solid-state circuit breaker 14 may determine that it outputs three-phase power and that its load is operating at a relatively high voltage that corresponds to an operating voltage of a large motor load, thus the solid-state circuit breaker 14 may automatically classify its electrical load 16 as a large motor based on this analysis.

In some cases, the control system 18 may use configuration interface techniques to receive thermal measurements and/or metering information directly from the solid-state circuit breaker 14. For example, the solid-state circuit breaker 14 may directly report values sensed by one or more measurement circuitries coupled to one or more portions of the solid-state circuit breaker 14 via updating of data stored in a table, data object, or the like, associated with the configuration interface between the solid-state circuit breaker 14 and the control system 18. As such, the solid-state circuit breaker 14 may report its sensed values including, but not limited to, ambient temperature, internal temperature, phase-to-phase voltage, internal voltage, phase-to-line voltage, current, frequency, power input, power output, or the like. Furthermore, in some cases, the solid-state circuit breaker 14 may report its status, such as whether it is operated in an open state (e.g., Open status), a closed state (e.g., Closed status), whether its closing/opening function is blocked and/or functionally prevented (e.g., Blocked status), and/or whether the solid-state circuit breaker 14 is non-operational and/or uncommunicative (e.g., offline) in the same data object associated with the configuration interface.

These various statuses, control operations, and other datasets may be communicated between the control system 18 and the solid-state circuit breaker 14 using any suitable communication or programming technique. For example, additional devices, such as the control system 18, may interface in real-time with the solid-state circuit breaker 14 using direct IEC® 61131 programming techniques and/or supporting programming languages, such as structured text, ladder logic, sequential function chart, functional block programming, or the like. It is noted that in some cases, the solid-state circuit breaker 14 may retain and/or generate an information log (e.g., such as within the storage 28) that may be reported to at a later time to the control system 18. The information log may store and/or track various alarm states, alerts, operations, sensed values, statuses, or the like generated by the solid-state circuit breaker 14.

One of the solid-state circuit breakers and/or the control system may initiate the communication. When communication is requested, the requesting device may self-report a desired communication frequency, such as a requested packet interval to use with the communication. As such, communication between the solid-state circuit breaker 14 and the control system 18 may be configurable at request to any real-time communication system needs, such as to dynamically adjust communications to a current bandwidth to be used to communicate with the control system 18. The requested packet interval may define a time period to use when transmitting information packets between the solid-state circuit breaker 14 and the control system 18.

The solid-state circuit breaker 14 and the control system 18 may communicate at the requested packet interval, and thus a data table of the control system 18 may populate at a rate proportional and/or based on the requested packet interval. When using the configuration interface-based communication techniques, the control system 18 may receive information from the solid-state circuit breaker 14 that includes logical tags (e.g., a logical tag corresponding to an identifier for the solid-state circuit breaker 14 and/or particular information regarding operation of the solid-state circuit breaker 14). Information reported to the control system 18 may be linked to the logical tags. The logical tags may be used in process or automation control strategies since the logical tag is static relative to the information reported as being associated with the logical tag (e.g., the logical tag may identify a reported value as a “circuit breaker X temperature,” such that each time information is reported with the logical tag, the information is stored at the control system 18 is a suitable location of the memory 26 and/or the storage 28).

Information from the solid-state circuit breaker 14 may be extracted in an operator-defined data type corresponding to the logical tag (e.g., P_SolidStateBreaker) that may encapsulate real-time data from the solid-state circuit breaker in an object-oriented model. The solid-state circuit breaker may be represented by one or more visualizations of the object-orientated model, and thus any displayed statuses of the solid-state circuit breaker may change in real-time as data transmits to the control system from the solid-state circuit breaker. For example, the solid-state circuit breaker 14 may be represented by one or more visualizations of the object-orientated model, and thus any displayed statuses of the solid-state circuit breaker 14 may change in real-time as data is transmitted to the control system 18 from the solid-state circuit breaker 14. A human-machine interface presented on a display of a computing device may present the object-orientated model. Furthermore, the logical tags and information from the solid-state circuit breaker 14 may feed computing applications to create a logical model of an MCC and/or electrical system that include the solid-state circuit breaker 14.

Keeping the foregoing in mind, FIG. 2 is a block diagram of a motor-feeder system 30, an example of the feeder system 10. FIG. 2 illustrates how the electrical load 16 may include a power converter 32, an inverter 34, a motor 36, and a direct current (DC) bus 38. The motor-feeder system 30 may be part of an industrial automation system. The motor-feeder system 30 may include the power converter 32 and the control system 18 that may control the operation of the power converter 32. The motor-feeder system 30 may also include one or more inverters 34. The inverters 34 may convert the DC voltage output by the power converter 32 into a controllable AC voltage used to power the motor 36.

In general, the power converter 32 may receive three-phase alternating current (AC) voltage from the AC power supply 12 and convert the AC voltage into a direct current (DC) voltage (e.g., voltage on DC voltage bus 38) suitable for powering a load (e.g., rectify a DC voltage based on the voltage from the AC power supply 12). It is noted that in some examples, the AC power supply 12 is replaced by a DC power supply, and the power converter 32 may operate to filter and/or improve a signal quality of the DC power supply. As such, the power converter 32 supplies a load, such as the one or more inverters 34, a DC voltage on the DC voltage bus 38. In certain embodiments, the one or more inverters 34 then convert the DC voltage to an AC voltage to be supplied to one or more devices connected to the inverters 34, such as motors 36. The one or more inverters 34 may then, in turn, control the speed, torque, or other suitable operation of the one or more devices (e.g., one or more motors 36) by controlling the AC voltage provided to the one or more devices. It should be understood that the industrial automation system may include one or more motor-feeder systems 30, and each of the motor-feeder systems 30 may include one or more additional components not depicted in FIG. 1 .

The power converter 32 may include any suitable power converter device that includes a number of switches that may be controlled. For example, the power converter 32 may be an active front end (AFE) converter, a diode converter, a thyristor converter, a diode front end rectifier, or the like. In some embodiments, the switches of the power converter 32 may be semiconductor-controlled devices, transistor-based (e.g., IGBT, MOSFET, or other suitable transistor) devices, or other suitable devices in which the opening and/or closing of the switch may be controlled using an external signal (e.g., gate signal), which may be provided by the control system 18. The power converter 32 may provide the DC voltage (e.g., a regulated DC output voltage) on a direct current (DC) bus 38, which may be provided to the inverters 34 and may regenerate extra or additional power back to the AC power supply 12 (or DC power supply). The power converter 32 may also operate to maintain a unity power factor, generate a stable DC voltage from the AC power supply 12 (or DC power supply), control a power factor transmitted to the one or more inverters 34, and the like to generally control power supplied to the one or more inverters 34.

As discussed above, the power converter 32 may use the switching frequencies of the switches (e.g., power conversion devices) to convert the voltage from the AC power supply 12 into the DC voltage. The DC voltage may be generated across a resistor-capacitor (RC) circuit 40 including one or more resistors and one or more capacitors. In addition, the control system 18 may control the operation of the power converter 32 to compensate for resonance, unknown line impedances, and the like.

The motor-feeder system 30 may be at least partially protected by use of the solid-state circuit breaker 14. When the solid-state circuit breaker 14 detects or receives a notification of an upstream fault and/or a downstream fault event, control circuitry of the solid-state circuit breaker 14 may cause the solid-state circuit breaker 14 to automatically open. In particular, the solid-state circuit breaker 14 may protect the motors 36 by opening in response to sensing one or more sensed parameters and determining that the one or more sensed parameters are greater than one or more threshold values corresponding to a desired operation of the motor-feeder system 30.

The figures described above have illustrated the solid-state circuit breaker 14 placed between the AC power supply 12 (or DC power supply) and the electrical load 16. However, in some cases, the solid-state circuit breaker 14 may be disposed after the power converter 32, as illustrated in FIG. 3 . In this case, the solid-state circuit breaker 14 may receive a DC voltage at its line-side and output a DC voltage at its load-side.

FIG. 3 is a block diagram of a non-motor-feeder system 42 protected by the solid-state circuit breaker 14. The solid-state circuit breaker 14 of FIG. 3 may be compatible with direct current (DC) supply voltages and/or DC supply currents (e.g., a generation system that generates DC supply voltages and/or DC supply currents). In the example non-motor-feeder system 42, one or more solid-state circuit breakers 14 may be coupled between a power converter 32 and one or more non-motor loads 44. FIG. 3 depicts one of many suitable uses of the solid-state circuit breaker 14.

Keeping the foregoing in mind, the solid-state circuit breaker 14 may be suitably used to protect a motor 36, a non-motor load 44, or both. Generally, the solid-state circuit breaker 14 may be coupled in line with a feeder bus for the electrical load 16. For example, the solid-state circuit breaker 14 may be coupled between an AC power supply 12 (e.g., a generator) and an electrical load 16 (e.g., motor 36, non-motor load 44).

A control system 18 may receive information from a solid-state circuit breaker 14 in the form of logical tags. These logical tags may be used in process or automation control strategies and may help to organize and/or identify incoming data to the control system 18. The information from the solid-state circuit breaker 14 may be extracted in an operator-defined data type (e.g., P_SolidStateBreaker) that may encapsulate real-time data from the solid-state circuit breaker 14 in an object-oriented model. In this way, the solid-state circuit breaker 14 may be represented by one or more visualizations of the object-orientated model, such as in a visualization rendered on a human-machine interface (HMI) (e.g., a visualized model of the industrial automation system associated with the solid-state circuit breaker 14). The object-oriented model may include displayed statuses of the solid-state circuit breaker 14 and/or data sensed by the solid-state circuit breaker 14. In some cases, the object-oriented model and/or a visualization of the object-oriented model may change in real-time as data is transmitted to the control system 18 from the solid-state circuit breaker 14. A human-machine interface presented on a display of a computing device may present the object-oriented model through one or more visualizations rendered on the display. Furthermore, logical tags and/or information from the solid-state circuit breaker 14 may feed computing applications to facilitate creating a logical model of an MCC itself. The control system 18 may use the computing applications to make control decisions, such as to decide when to electrically open or electrically close the solid-state circuit breaker 14. In some cases, the solid-state circuit breaker 14 may be coupled to the electrical load 16 to replace a motor starter as well as to protect the electrical load 16 from undesired power supply signals.

When using the solid-state circuit breaker 14 as a motor starter, the solid-state circuit breaker 14 may be operated to perform a reverse starting operation, a non-reverse (e.g., forward) starting operation, and a soft-start starting operation (e.g., stepped starting operation) to guide the power-on (e.g., starting) of a motor load. While performing starting or steady state operations, the solid-state circuit breaker 14, as a single device, may perform similar operations of multiple devices (e.g., galvanic disconnecting devices, contactors, thermal overload protection devices) while using circuitry within a same physical enclosure. This may permit the three devices (e.g., galvanic disconnecting devices, contactors, thermal overload protection devices) to be replaced by the solid-state circuit breaker 14 in a starter. To operate the solid-state circuit breaker 14 in the reverse starting operation or the non-reverse starting operation, one or more solid-state circuit breakers 14 may be closed in a particular order to cause the electrical load (e.g., motor 36) to rotate either in a reference direction (e.g., non-reverse) or against the reference direction (e.g., reverse). With a soft-start starting operation, the control system 18 may operate one or more solid-state circuit breakers 14 according to device profiles that define operational ranges for respective devices while powering on the electrical load 16.

FIG. 4 is a flowchart of a method 60 performed by the control system 18 to control a soft-start operation of the electrical load 16 (e.g., motor 36, non-motor load 44). Although the method 60 is described below as performed by the control system 18, it should be noted that the method 60 may be performed by any suitable processor that controls operation of the solid-state circuit breaker 14 and/or of the motor 36. Moreover, although the following description of the method 60 is described in a particular order, it should be noted that the method 60 may be performed in any suitable order.

At block 62, the control system 18 may initiate a soft-start operation according to a start-up profile of the solid-state circuit breaker 14 and/or the electrical load 16. Each solid-state circuit breaker 14 and/or electrical load 16 may correspond to a start-up profile. A start-up profile for the electrical load 16 may define a duration of time to use to ramp up average supply voltages and/or supply currents to the electrical load 16, a direction of signals to use to start the load (e.g., forward direction signals or reverse direction signals relative to the reference direction), a frequency of electrical switching (e.g., solid-state switching) to use when starting the electrical load 16, or the like. Each solid-state circuit breaker 14 and/or electrical load 16 may correspond to a unique and/or individually defined start-up profile. Start-up profiles may be stored in memory 26 and/or storage 28 of the control system 18, or in any suitable storage device accessible by the control system 18, such as in a cloud-based and/or Internet-based storage system.

After the start-up profile is loaded and/or accessed by the control system 18, the control system 18 may generate control signals in accordance with the start-up profile, thereby operating the solid-state circuit breaker 14 in accordance with its corresponding start-up profile. Start-up profiles may be associated with configuration interface-based communication techniques and/or may permit individualized operation of each solid-state circuit breaker 14 coupled to the control system 18. For example, the solid-state circuit breaker 14 may receive configurations and/or transmit statuses to the control system 18 using specific references to portions of a data table or data object. In this way, the control system 18 may reference the data table or data object to determine how to start-up the electrical load 16 coupled to the solid-state circuit breaker 14 (e.g., by referencing the start-up profile). While the control system 18 operates the solid-state circuit breaker 14 according to the start-up profile, the control system 18 may receive and monitor various operational statuses of the electrical load 16 and/or of the solid-state circuit breaker 14 during the start-up process. In some cases, operational statuses may be summary reports (e.g., “on,” “closed,” “off,” “open”) and/or may be numbers or values indicative of sensed data received from sensing devices. For example, the solid-state circuit breaker 14, such as using a processor associated with the solid-state circuit breaker 14, may generate an operational status in response to operating to open (e.g., decouple its line-side from its load-side).

Thus, at block 64, the control system 18 may monitor data (e.g., operational statuses) regarding operational parameters including voltage, current, temperature, humidity, and the like, of the solid-state circuit breaker 14 and/or the electrical load 16 during start-up of the electrical load 16. For example, soft-starting the motor 36 may involve operating the motor 36 within defined operational parameter ranges (e.g., expected value ranges). Thus, the control system 18 may monitor data from the solid-state circuit breaker 14 and/or the motor 36 to determine how to operate one or more solid-state circuit breakers 14 to soft-start the motor 36, such that the operating parameters remain at values within respective operational parameter ranges. Thus, the respective operational parameter ranges may correspond to desired parameter ranges during start of the motor 36. When the control system 18 determines one or more of the operational parameters is greater than or less than an expected value, the control system 18 may adjust an operation of the electrical load 16 and/or the solid-state circuit breaker 14 to compensate for the deviation.

At block 66, the control system 18 may operate the solid-state circuit breaker 14 to open as part of overload protection operations based at least in part on the data representative of the operational parameters. The opening of the solid-state circuit breaker 14 may be triggered in response to detecting a fault associated with a supply line or a load line of the solid-state circuit breaker 14. Opening the solid-state circuit breaker 14 may prevent a fault from damaging the electrical load 16. In some cases, the control system may detect a deviation from a start-up profile corresponding to the motor 36 and may cause the solid-state circuit breaker 14 to open in response to detecting the deviation. It is noted that in some cases, the control system 18 may cause the solid-state circuit breaker 14 to close after opening. For example, when soft-starting the motor 36, the solid-state circuit breaker 14 may open and closed at different times to simulate contactor driving schemes, where different portions (e.g., poles) of the solid-state circuit breaker 14 may drive different lines between the solid-state circuit breaker 14 and the motor 36.

Keeping the foregoing in mind, the solid-state circuit breaker 14 may be characterized by various physical characterizations. For example, the solid-state circuit breaker 14 may perform electrical isolation operations without employing devices that switch using a mechanical apparatus (e.g., electromagnetic and/or coil-based switching devices). Furthermore, the solid-state circuit breaker 14 may perform operations of galvanic disconnecting devices, contactors, and thermal overload protection devices using solid-state semiconductor circuitry disposed within a same physical enclosure within a housing unit. This may permit the three devices (e.g., overload protection circuitry, disconnect switching circuitry, and motor controlling circuitry) to be replaced by one or more solid-state circuit breakers 14.

To elaborate, FIG. 5 is a block diagram of a starter system 80 and a starter system 82 that uses the solid-state circuit breaker 14. As shown, the starter system 80 includes three distinct physical components: one or more galvanic disconnecting devices 84 with one or more branch circuit protection devices 86 (e.g., circuit breaker, fused disconnect switch), one or more contactors 88 (e.g., isolating devices), and one or more thermal overload protection devices 90 (e.g., electronic overload). These three components work together as an assembly to provide a full voltage non-reversing starter system control operation of the motor 36. For example, the galvanic disconnecting devices 84 may open to provide an air gap between a line-side feeding the solid-state circuit breaker 14 and the solid-state circuit breaker 14. When the galvanic disconnecting devices 84 are closed, contactors 88 may be opened and/or closed in accordance with various starting and/or powering-on patterns, such as to soft-start the motor 36. While each of the contactors 88 are closed, the thermal overload protection devices 90 may respectively monitor each line to the motor 36 to protect against unsuitable operation of the starter system 80. For example, the thermal overload protection devices 90 may decouple the motor 36 from the contactors 88 if one of the lines were to exceed a thermal threshold and/or otherwise becomes unsuitable for operations.

The solid-state circuit breaker 14 may improve on other starter technologies by enabling the contactors 88 and the thermal overload protection devices 90 to be replaced by the solid-state circuit breaker 14. For example, the control system 18 may operate according to firmware (e.g., software and/or instructions stored in the memory 26 or storage 28 executable by the processor 24 to cause the control system 18 to perform control operations on the solid-state circuit breaker 14) to mimic operations performed by the contactors 88 and/or the thermal overload protection devices 90. The control system 18 may load one or more start-up profiles. The control system 18 may drive the solid-state circuit breaker 14 based on a respective of the start-up profile to change signals output from the solid-state circuit breaker 14. For example, the control system 18 may cause a first terminal (T1) 92A, or any of the terminals, to transmit signals from the line-side before a second terminal (T2) 92B, or any of the terminals, consistent with an example operation of the starter system 80. The control system 18 may operate the solid-state circuit breaker 14 according to one or more thermal models. A thermal model may set overcurrent thresholds and/or monitoring ranges and/or define permitted or impermissible changes in transmitted current (e.g., Δdi/Δdt) based at least in part on motor curves of the motor 36 (e.g., expected outputs from the motor 36 in response to inputs).

In this way, when the control system 18 receives sensing data from one or more current sensors and/or voltage sensors, the control system 18 may predict whether an overcurrent event is statistically likely to occur based on one or more thermal modes. For example, the solid-state circuit breaker 14 may include one or more current transformers to sense currents associated with the solid-state circuit breaker 14 and/or one or more potential transformers to sense voltages associated with the solid-state circuit breaker 14, and the control system 18 may use the voltages and/or currents when determining how to operate the solid-state circuit breaker 14. The control operations of the control system 18 may involve analyzing a thermal model of the motor 36, inputs to and/or outputs from the solid-state circuit breaker 14, a thermal model of the solid-state circuit breaker 14, or the like. For example, the control system 18 may analyze time-current characteristic curves of the solid-state circuit breaker 14 defined in the model to determine when to open the solid-state circuit breaker 14. In some cases, the control system 18 may monitor changes in current transmitted (e.g., Δdi/Δdt) from the solid-state circuit breaker 14 to determine when changes in current are happening relatively too fast and/or at a rate that is greater than (or otherwise outside of) a threshold value defined by the thermal model of the motor 36. In this way, since the starter system 82 includes the solid-state circuit breaker 14 capable of operating to protect the solid-state circuit breaker 14 and/or the motor 36 similar to the contactors 88 and/or the thermal overload protection devices 90, the starter system 82 may not include the contactors 88 and/or the thermal overload protection devices 90.

In some cases, a reversing starter capable of driving the motor 36 in a forward or a reverse (e.g., non-forward) direction is used to drive the motor 36. To elaborate, FIG. 6 is a block diagram of a reversing starter 100 and a reversing starter 102. To form a reversing starter, one or more contactors 88B are added to certain starters and interlocked with the contactors 88 (e.g., contactors 88A) to provide electrical phase reversal of two phases. For example, contactors 88A are interlocked with contactors 88B of the reversing starter 100. By interlocking the contactors 88 and swapping phases (e.g., first line (L1) and third line (L3) at the load-side of the contactors 88B relative to the load-side of the contactors 88A), either contactors 88A or contactors 88B may be engaged in the “on” position at a same time. Since the second contactor 88B has two electrical phases swapped (e.g., L1, L3), the electrical phase rotation is 180 degrees from the first contactor 88A, and thus may drive the motor 36 in the reverse direction.

Similar to the starter system 80 and the starter system 82 of FIG. 5 , inclusion of the solid-state circuit breaker 14 in the reversing starter 102 may permit removal of the contactors 88 (e.g., contactors 88A and contactors 88B) and the overload protection devices 90. In this way, the solid-state circuit breaker 14 may couple (e.g., directly couple) between a power supply (e.g., AC power supply 12) and/or line-side of the motor 36 and the motor 36. Furthermore, in some embodiments, the solid-state circuit breaker 14 may include a mechanical air gap that provides the galvanic isolation that the galvanic disconnecting devices 84 provide, thereby permitting removal of the galvanic disconnecting devices 84 from the reversing starter 102.

In the cases of the starter system 82 of FIG. 5 and the reversing starter 102 of FIG. 6 , branch circuit protection provided by the galvanic disconnecting devices 84 may be provided as a function of the solid-state circuit breaker 14. For example, the solid-state circuit breaker 14 may be capable of providing circuit interruption and/or short circuit protection suitable to various standards of electrical governing bodies based at least in part on control operations of the control system 18 operating the solid-state circuit breaker 14 in accordance with the standards. Furthermore, in some embodiments, the solid-state circuit breaker 14 may include an integrated air-gap disconnect and/or integrated galvanic disconnecting device to further isolate the solid-state circuit breaker 14 in the event of a fault occurring (e.g., isolate in addition to any air-gap function of the solid-state circuit breaker 14).

To elaborate, FIG. 7 is an illustration of a housing unit 110 for the solid-state circuit breaker 14, where the solid-state circuit breaker 14 may be disposed within the housing unit 110. The housing unit 110 may include a mechanical device 112 designed to operate a galvanic disconnecting device associated with (e.g., galvanic disconnecting devices 84) and/or disposed within the solid-state circuit breaker 14, providing mechanical galvanic isolation. The mechanical device 112 may include a latch device 114 (e.g., spring that operates interconnecting devices) to decouple a supply-side (e.g., line-side) from a load-side of the solid-state circuit breaker 14 using the galvanic disconnecting device for maintenance access or withdrawal of the housing unit 110. For example, the mechanical device 112 may operate to interlock the housing unit 110 and/or drawer door of the housing unit 110 with the latch device 114 and/or a device coupled or operable by the latch device 114.

When interlocked, the solid-state circuit breaker 14 may not be removed from a cabinet space within a motor control center and/or an installation site based at least in part on the latch device 114 locking the solid-state circuit breaker 14 in place. For example, the latch device 114 may control a position on an axis 116 of a metal plate 118. When a handle 120 of the housing unit 110 is operated into an “off” position (e.g., when the solid-state circuit breaker 14 is de-energized), the latch device 114 may pull the latch device 114 taught, causing the metal plate 118 to move upward on the axis 116. This motion may adjust any interlocking circuitry of the solid-state circuit breaker 14 to permit removal of the solid-state circuit breaker 14 from a motor control center cabinet and/or from the housing unit 110. When the handle 120 is operated into an “on” position (e.g., when the solid-state circuit breaker 14 is energized) and/or a “trip” position (e.g., de-energized in response to an undesired operation), the latch device 114 may release the latch device 114, causing the metal plate 118 to move downward on the axis 116. The metal plate 118 moving downward on the axis 116 may adjust at least some interlocking circuitry of the solid-state circuit breaker 14 to block access to the solid-state circuit breaker 14. In this way, the solid-state circuit breaker 14 may be mechanically blocked from being accessed (e.g., being removed from a motor control center cabinet and/or from the housing unit 110, being opened for inspection and/or maintenance) while the solid-state circuit breaker 14 is energized and/or in a trip state (e.g., permitting removal when the handle 120 is in an “off” position as opposed to “on” or “trip”).

In this way, when the solid-state circuit breaker 14 is not energized, the mechanical device 112 may permit removal of the solid-state circuit breaker 14 from the cabinet space and/or the installation site based at least in part on the latch device 114 being operated into an orientation that permits such removal. Interlocking capabilities of the solid-state circuit breaker 14 may be provided additionally or alternatively to interlocking capabilities of the housing unit 110, such that a combination of a position of the handle 120 and an operational state of the solid-state circuit breaker 14 may permit or deny removal of the solid-state circuit breaker 14. For example, one or more sensed values may be used by the control system 18 to unlock or lock interlocking circuitry of the solid-state circuit breaker 14, such as in response to detecting no voltage or no current conditions within or from the solid-state circuit breaker 14. In some embodiments, a defeating mechanism may be included to override any interlocking devices of the solid-state circuit breaker 14, such as a key that a user may use to override an interlocking device.

Additionally or alternatively, an integrated air-gap disconnect device may be used with the solid-state circuit breaker 14, such as alone or in combination with the mechanical device 112. The integrated air-gap disconnect device may be associated with a push button. When the push button is pressed, interlocking circuitry may disengage and permit retraction springs to pull contacts of the solid-state circuit breaker 14 away from each other to form an air gap between the contacts. For example, the integrated air-gap disconnect device may cause galvanic isolation between a supply-side and a load-side of the solid-state circuit breaker 14 in response to the latch device 114 being extended by movement of the handle 120. Powering-down electronics of the solid-state circuit breaker 14 before operating the integrated air-gap disconnect device may reduce a likelihood of arcing occurring when the air gap is being formed between the contacts.

The control system 18 may use the integrated air-gap disconnect when performing lockout/tagout control operations and/or when electrically isolating devices coupled downstream of the solid-state circuit breaker 14 from devices coupled upstream of the solid-state circuit breaker 14. Integrated air-gap disconnects may be used in combination with air gaps provided internal to the solid-state circuit breaker 14 and/or in combination with interlocking circuitry of the housing unit 110. In some cases, additional external disconnect switches may be used in combination with solid-state circuit breakers 14 to further electrically disconnect a line-side of the solid-state circuit breaker 14 from the solid-state circuit breaker 14.

For example, FIG. 8 is an illustration of a cabinet 130 that includes the housing unit 110 and the solid-state circuit breaker 14. The housing unit 110 may also include one or more upstream switches 132. In this example system, the galvanic disconnecting device 84 may be replaced by the solid-state circuit breaker 14 coupled to additional circuit breakers or fused disconnect switches (e.g., upstream switches 132) upstream from the solid-state circuit breaker 14. The upstream switches 132 may respectfully couple to each line feeding the solid-state circuit breaker 14 (e.g., L1, L2, L3). Each upstream switch of the upstream switches 132 may couple in series with the solid-state circuit breaker 14 to provide disconnecting circuit isolation. The upstream switches 132 may be used in combination with any of the systems and/or methods described herein. The handle 120 may electrically disconnect the solid-state circuit breaker 14 and/or the upstream switches 132. In some cases, the upstream switches 132 may automatically isolate the solid-state circuit breaker 14 from one or more power supplies in response to the upstream switches 132 detecting a change in transmitted current (e.g., Δdi/Δdt). The upstream switches 132 may be used to decouple the solid-state circuit breaker 14 from the line-side of the solid-state circuit breaker 14 additional to or alternative of an integrated air-gap disconnect.

When operating, the solid-state circuit breaker 14 may generate heat since semiconductor circuitry tends to produce heat when conducting currents. Thermal management systems may be installed within a motor control center assembly to dissipate and remove heat from air ambient to the solid-state circuit breakers 14.

For example, FIG. 9 is an illustration of the housing unit 110 including the solid-state circuit breaker 14 and an example thermal management device 140. The thermal management device 140 may couple the solid-state circuit breaker 14, such as through metal of the housing unit 110. Coupling the solid-state circuit breaker 14 to the thermal management device 140 may provide a path to dissipate thermal energy generated by the solid-state circuit breaker 14. In the depicted example, the thermal management device 140 is a heat sink formed from aluminum or other suitable material and coupled to the solid-state circuit breaker 14. In some cases, the thermal management device 140 may reduce a temperature of the solid-state circuit breaker 14 by leveraging conduction for temperature control, such as through passive air conduction and/or through active air conduction (e.g., pressurized air being passed over conduction paths). In some cases, a thermal connection between the solid-state circuit breaker 14 and the thermal management device 140 may be a heat pipe design that leverages passive air conduction and/or active air conduction.

The thermal management device 140 of FIG. 9 is depicted as mounted in a north-south orientation such that fins 142 of the thermal management device 140 may be orientated perpendicular to a ground plane. In this way, the ground plane may correspond to an orientation of the x-y-axis and the fins 142 of the heat sink may follow an orientation of the z-axis. In some cases, positioning the fins 142 such that air may conduct through the fins 142 following the z-axis may enhance cooling capabilities of the thermal management device 140 since air is able to efficiently conduct upwards between air gaps 144 of the fins 142.

When installing one or more solid-state circuit breakers 14 in an enclosure, sometimes no isolation is provided between adjacent solid-state circuit breakers 14. In this way, when one of the solid-state circuit breakers 14 is to be accessed, each solid-state circuit breaker 14 within the enclosure may be powered down and/or be brought to an operational state suitable for access. This enclosure may be improved if each of the solid-state circuit breakers 14 are installed to have respective hinged covers and individual enclosures around each solid-state circuit breaker 14.

FIG. 10 is an illustration of an enclosure 154, such as the cabinet 130 of FIG. 8 , storing multiple housing units 110, and thus multiple solid-state circuit breakers 14, and an example thermal management device 140. Respective enclosures 156 may permit each respective solid-state circuit breaker 14 to be accessed without having to power-off and/or isolate the targeted solid-state circuit breaker 14 from a nearby solid-state circuit breaker 14. Providing multiple solid-state circuit breakers 14 in separate enclosures 156 disposed within the enclosure 154 may improve industrial automation system deployment since the individual solid-state circuit breakers 14 and corresponding load wires may be serviced or replaced while power is still applied to the other solid-state circuit breakers 14.

Each respective enclosure 156 within the enclosure 154 may couple to a wire gutter 158 (e.g., wire pathway, “wireways”) to permit organization of wires incoming or outgoing to respective of the solid-state circuit breakers 14. This infrastructure may permit adjacently stored solid-state circuit breakers 14 (e.g., adjacent within an enclosure 154 but individually enclosed within additional, nested enclosures 156) to share a common bus 160. The common bus 160 may permit transmission of electrical signals from the power supply 12 to each of the solid-state circuit breakers 14 (e.g., from a power distribution network common power supply). In this way, each of the solid-state circuit breakers 14 may share a common line side, and/or a common power supply for control signals and/or status signals.

Furthermore, the common bus 160 may permit a common communication backplane to be provided to the solid-state circuit breakers 14. In this way, while each solid-state circuit breaker 14 may be disposed within separate housing enclosures 156, the individual solid-state circuit breakers 14 may share one or more inputs or conduction pathways with each other.

In some cases, the solid-state circuit breakers 14 may attach to a power distribution bus via plug-in connections, bolt-on connections, or the like (e.g., terminal blocks 162). Furthermore, each of the solid-state circuit breakers 14 may couple and/or power respective electrical loads 16 via outputs from the respective terminal blocks 162. In this way, the multiple solid-state circuit breakers 14 may be supplied from a same power supply 12 and protect and/or output to one or more electrical loads 16. Furthermore, each solid-state circuit breaker 14 may include a display 164. Each display 164 may present status information and/or sensed values associated with the respective solid-state circuit breaker 14.

The enclosure 154 may provide a thermal management device 140 to be shared by each of the solid-state circuit breakers 14, such as a common heatsink or common fan assembly (e.g., for active air conduction cooling methods). The solid-state circuit breakers 14 may provide temperate control to one or more of the solid-state circuit breakers 14 at a substantially similar time. For example, the solid-state circuit breakers 14 may mate with a common heatsink surface of the thermal management device 140 by direct metal-to-metal contact between the common heatsink surface and each respective solid-state circuit breaker 14 (e.g., a metal surface of each enclosure 156). In some cases, the metal-to-metal contact between the surfaces is smooth, is an interface of cross-hatch embossed patterns, or any combination of therein. For example, one solid-state circuit breaker 14 may use a smooth contact between the surfaces while a different solid-state circuit breaker 14 may use a non-smooth contact between the surfaces.

Additionally or alternatively, a cradle that enables withdrawal of the solid-state circuit breaker 14 from the enclosure 154 may be installed for each solid-state circuit breaker 14 to improve ease of connection or disconnection of the solid-state circuit breaker 14 from the common bus 160 and/or thermal management device 140. For example, the cradle may couple prongs of the solid-state circuit breaker 14 to prongs associated with the common bus 160 and/or the thermal management device 140. The cradle may be designed to retrofit to the solid-state circuit breaker 14. Similarly, the control system 18 may be coupled to the common bus 160 and/or the thermal management device 140, while having a separate housing to isolate the control system 18 from the solid-state circuit breakers 14. The enclosure 154 assembly may be provided in a larger overall enclosure with a power bus (e.g., a portion of the common bus 160 disposed between the enclosure 154 and the power supply 12) to permit the common bus 160 to be fed from an adjacent enclosure, such as an adjacent motor control center, switchboard, switchgear power distribution bus, or the like.

It is noted that a hinged door is used for the example enclosure 156 shown in FIG. 10 . It should be understood that any suitable door or system may be used to control access to the solid-state circuit breaker 14. For example, the enclosure 156 may enclose the solid-state circuit breaker 14 such that a viewing window 166 is not present. Furthermore, the enclosure 156 may include a hinge on any side of the enclosure 156 (e.g., left-side, right-side, top-side, bottom-side) or the like. The enclosure 156 and/or the enclosure 154 may be of any suitable geometry and/or the wire gutters 158 may include any suitable wires associated with the solid-state circuit breaker 14, such as to improve organization of the wires within the enclosure 154.

It is noted that the solid-state circuit breaker 14 may be controlled by the control system 18 using a variety of communication methods, and thus the common bus 160 and/or the wire gutters 158 may include a variety of communicative couplings to permit communication between respective solid-state circuit breakers 14 and the control system 18. For example, the communication methods may include using hardwired inputs and/or hardwired outputs, FIELDBUS® networks (e.g., controller area network (CAN), CANBUS®), Ethernet networks (e.g., Ethernet/IP, MODBUS® transmission control protocol (TCP)), wireless communications, near field communications (e.g., BLUETOOTH®, ZIGBEE®), or Mesh-type communications), or the like. It is also noted that the solid-state circuit breaker 14 may interface to a graphical user interface associated with a centralized control system and/or engineering workstation communicatively coupled to the control system 18.

Additionally or alternatively, the solid-state circuit breaker 14 may also include an internal control system within the housing unit 110 and/or each enclosure 156. The internal control system may perform local control operations, such as opening the solid-state circuit breaker 14 in case of internally detected fault or other local operating condition. When both the internal control system and the control system 18 are used, the internal control system may respond to local (e.g., micro-scale) operating conditions while the control system 18 may respond to global and/or system-level (e.g., macro-scale, unit-wide) operating conditions. In this way, when the control system 18 detects a fault upstream of the solid-state circuit breaker 14, the control system 18 may generate one or more commands (e.g., control commands) to cause the solid-state circuit breaker 14 to operate (e.g., open in case of a fault condition) in response to the system-level operating condition. Similarly, when the internal control system detects a fault internal to the housing unit 110, the internal control system may operate the solid-state circuit breaker 14 to open. The internal control system, in some cases, may operate the solid-state circuit breaker 14 without explicit command from the control system 18 (e.g., independent of control command from a processor of the control system 18) and may notify the control system 18 after operating the solid-state circuit breaker 14 of the fault and/or operation (e.g., by generating a notification and/or message after the opening of the solid-state circuit breaker 14). The control system 18 may even perform an operation in response to the notification from the internal control system. For example, the control system 18 may further disconnect the electrical load from the power supply 12 by opening a switch in response to the notification, such as galvanic disconnecting devices 84 coupled between the power supply and the solid-state circuit breaker 14. The internal control system of the solid-state circuit breaker 14 may also operate a portion of the solid-state circuit breaker 14. For example, the SiC switches of the solid-state circuit breaker 14 may be able to be partially driven by the internal control system. This may permit a change in output on each of various output load lines of the solid-state circuit breaker, such that a first line (L1) and/or first terminal (T1) may output a voltage at a different frequency and/or at a different time than a second line (L2), a second terminal (T2), third line (L3), and/or a third terminal (T3). It is noted that in some cases, the solid-state circuit breaker 14 may use firmware to change a relative phase and/or amplitude of the output electrical signals relative to the input electrical signals, such as to drive the motor 36 according to a forward starting configuration or a reverse starting configuration. In this way, the solid-state circuit breaker 14 may be capable of reversing a rotation associated with its output phases without using the contactors 88.

Furthermore, different operators may have different levels of authentication that permit the different operators varying control and/or access levels to the operation of the solid-state circuit breaker 14. Indeed, some operator profiles (e.g., user profiles) may have different levels of access to information associated with operation of the solid-state circuit breaker 14. For example, some operators may have higher or lower permission profiles than other operators. Different permission profiles may permit some operators to operate the solid-state circuit breaker 14 (e.g., using the control system 18) to open or close and/or check a status of the solid-state circuit breaker 14, while some operators are permitted to check the status of the solid-state circuit breaker 14 without having permission to operate the solid-state circuit breaker 14 open or close. The permission profiles may also be used in combination with the mechanical device 112 and/or interlocking circuitry of the solid-state circuit breaker 14 to selectively permit or deny access to the solid-state circuit breaker 14.

In some cases, the permission profiles may be used to provide a first user with a first level of control associated with the solid-state circuit breaker 14 and to provide a second user with a second level of control associated with the solid-state circuit breaker 14, where the first level of control and the second level of control may be different. User profiles may define a level of control assigned to the respective user. For example, a user having a first characterization may be permitted to access hardware and software of a solid-state circuit breaker 14 while a different user having a second characterization may be permitted to only access hardware of the solid-state circuit breaker 14 without having permission to access software of the solid-state circuit breaker 14. User authorization levels may be maintained via the different characterizations of users and stored within a user profile accessible by control circuitry of a motor control center. Furthermore, user authorization levels may be device-specific (e.g., such that one operator trained on a solid-state circuit breaker 14 may or may not have authorization to operate on a chain of solid-state circuit breakers 14), unit-specific (e.g., referring to a portion of an industrial automation facility-such that operators may be set to operate within specific portions of the industrial automation system), or any suitable granularity of operation or control. In some cases, user authorization levels may be set to expire after a duration of time, which may correspond to training procedures associated with the industrial automation facility. For example, an operator may be trained on how to remove the solid-state circuit breaker 14 but that training may need to be renewed each year anniversary of the original training. In some cases, the control system 18 may determine when that operator is trying to access the solid-state circuit breaker 14 and inform the operator that the training is set to expire, or, when a current date or time is a threshold of time close to the expiration date or time, is close to expiring. Furthermore, when the training of the operator expires, the control system 18 may adjust or remove the authorization granted to the operator (e.g., the control system 18 may update the user profile to reflect the change in authorization).

In some cases, a solid-state circuit breaker 14 may also be operated using selective coordination schemes. For example, a group of solid-state circuit breakers 14 may be logically grouped on some electrical loads 16, such as elevators, life-critical loads, standby power systems, high-value assets, or the like, as a way manage power supplied to the electrical loads 16 during abnormal electrical conditions. Two devices that monitor overcurrent and/or overvoltage conditions may be selectively coordinated (e.g., operated in accordance with and/or using selective coordination schemes) when a downstream overcurrent device relatively nearest to a fault opens before a corresponding upstream overcurrent device opens. Overcurrent protection schemes may use one or more solid-state circuit breakers 14, one or more different protection devices, or any combination thereof, to protect the electrical loads 16.

Gateway Interface for Solid-State Circuit Breaker

Furthermore, in some embodiments, a solid-state circuit breaker may include a controller area network (CAN) communicative coupling (e.g., CANBUS®) and/or an internet protocol (IP)-based communicative coupling, such as an Ethernet IP communicative coupling and/or Ethernet IP, to a control system. These communicative couplings may enable the solid-state circuit breaker to directly communicate with the control system (e.g., a microcontroller) and/or an enclosure (e.g., a cabinet) without a host computer. In certain embodiments, the solid-state circuit breaker may be utilized in low voltage applications (e.g., less than 1000 volts).

Keeping the foregoing in mind, FIG. 11 is a block diagram of the motor-feeder system 30 that includes a gateway interface device 172. The gateway interface device 172 may be communicative coupled to the solid-state circuit breaker 14. In some embodiments, the gateway interface device 172 may include any number of communication interfaces, such as a controller area network (CAN) communicative coupling (e.g., CANBUS®) an internet protocol (IP)-based communicative coupling, such as an Ethernet IP communicative coupling and/or Ethernet internet protocol (IP), or other suitable communication protocol interfaces. The gateway interface device 172 may include a user interface and/or logically-defined data object (e.g., data table) that permits the gateway interface device 172 to provide and/or update a configuration and/or obtain a status of the solid-state circuit breaker 14. In this way, the gateway interface device 172 may be a data boundary used to translate data received from devices external to the solid-state circuit breaker 14 to a format readable by the solid-state circuit breaker 14 and/or to translate statuses from the solid-state circuit breaker 14 into a format readable by devices external to the solid-state circuit breaker 14. Indeed, a graphical user interface managed by the control system 18 may enable a user to enter or adjust configurations of the solid-state circuit breaker 14 by changing information stored in the gateway interface device 172.

In some embodiments, the gateway interface device 172 may perform a format translation of data associated with it, such as to change a data type or length. The gateway interface device 172 may include at least one processor and at least one memory, such as the control system 18 described above. In some embodiments, the memory may include one or more tangible, non-transitory, computer-readable media that store instructions executable by the processor and/or data to be processed by the processor. For example, the memory may include random access memory (RAM), read only memory (ROM), rewritable non-volatile memory such as flash memory, hard drives, optical discs, and/or the like. Additionally, the processor may include one or more general purpose microprocessors (ASICs), one or more field programmable logic arrays (FPGAs), or any combination thereof.

Node addresses, protection settings (e.g., analog settings, discrete settings), or the like may each be set, reset, and/or defined via data stored in the memory of the gateway interface device 172. The memory may also serve as a table of parameters to store configurations in an offline place for download when a replacement of a solid-state circuit breaker is to occur. This may improve start-up or replacement operations of the industrial automation system by reducing downtime associated with a replacement or maintain operation of the solid-state circuit breaker 14 (e.g., since the configuration is relatively easy to download and upload into a device replacement for the solid-state circuit breaker).

With the foregoing in mind, FIG. 12 is a block diagram of a gateway interface device, such as the gateway interface device 172 of FIG. 11 , in accordance with an embodiment of the present disclosure. The gateway interface device 172 may include a controller 174, a power supply 178, and a set of communication interfaces, such as a solid-state circuit breaker interface 176, an Ethernet Device Level Ring (DLR) interface 180, a subnet interface 182, and an expansion bus interface 184, and a set of corresponding communication ports 186, 188, 190, 192, and 194. The controller 174 may be provided in the form of a computing device, such as a programmable logic controller (PLC). The controller 174 may include at least one processor and at least one memory. In some embodiments, the memory may include one or more tangible, non-transitory, computer-readable media that store instructions executable by the processor and/or data to be processed by the processor. Further, the memory may store data obtained via the set of communication interfaces and/or algorithms utilized by the processor to control operation of the solid-state circuit breaker 14. The processor may process acquired data and/or may translate acquired data to provide communication between the solid-state circuit breaker 14 and any number of devices communicatively coupled to the gateway interface device 172 by the set of communication interfaces. In some embodiments, the power supply 178 may provide power for operation of one or more components of the gateway interface device 172 (e.g., controller 174). The power supply 178 may be a voltage power supply (e.g., 12V).

In certain embodiments, the solid-state circuit breaker interface 176 may be a Controller Area Network (CAN) Flexible Data-Rate (FD) communication interface. The solid-state circuit breaker interface 176 may enable communication between the gateway interface device 172 and the solid-state circuit breaker 14. The controller 174 may receive and/or may generate (e.g., translate) one or more data signals (e.g., instructions, commands) in the CAN FD communication protocol. The controller 174 may transmit one or more data signals in the CAN FD communication protocol to the solid-state circuit breaker 14 via the solid-state circuit breaker interface 176 and the corresponding communication port 186. Likewise, the controller 174 may receive data signals in the CAN FD communication protocol from the solid-state circuit breaker 14 via the solid-state circuit breaker interface 176 and the corresponding communication port 186. In certain embodiments, the controller 174 may generate and/or may transmit a data signal corresponding to an instruction to turn on (e.g., energize) the solid-state circuit breaker 14, a data signal corresponding to an instruction to trip (e.g., de-energize) the solid-state circuit breaker 14, and the like. Additionally or alternatively, the controller 174 may receive an indication (e.g., data signal) corresponding to an operational status of the solid-state circuit breaker 14.

In some embodiments, the Ethernet DLR interface 180 may enable communication between the gateway interface device 172 and any number of nodes on a DLR network. A node of a DLR network may be classified as a ring supervisor or a ring participant. A ring supervisor may manage traffic on the DLR network and may collect diagnostic information associated with the DLR network. The ring supervisor may reconfigure the ring network after the occurrence of a network fault. Each DLR network may require at least one node to be configured as a ring supervisor. In certain embodiments, the DLR network may include one or more backup ring supervisors in case of a fault or issue associated with the primary ring supervisor. A ring participant may process one or more data signals transmitted over the DLR network and/or may pass one or more data signals onto a subsequent node on the DLR network. Additionally or alternatively, a ring participant may report fault locations to the ring supervisor. A ring participant may reconfigure the ring network in response to a network fault and may relearn a ring network topology.

In certain embodiments, the Ethernet DLR interface 180 and the corresponding communication port 188 may enable communication and/or control of the solid-state circuit breaker by an external computing device, such as a programmable logic controller (PLC), a distributed control system (DCS), and the like. In some embodiments, the Ethernet DLR interface 180 may enable communication between the gateway interface device 172, an ethernet switch 196, and/or a variable frequency drive 198. The variable frequency drive 198 may vary operational parameters (e.g., frequency and voltage) for a motor to control the motor speed and/or the motor torque.

In certain embodiments, the subnet interface 182 may be an Ethernet subnet communication interface. In some embodiments, the subnet interface 182 may enable communication between the gateway interface device 172 and any number of devices via a subnet. A subnet is a logical partition of a network and each device connected to the subnet may have a portion (e.g., identifier) of an associated IP address that corresponds to the subnet. In certain embodiments, the controller 174 may receive and/or may translate data signals between the CAN FD communication protocol and the Ethernet subnet communication protocol to facilitate control and command of the solid-state circuit breaker 14.

In some embodiments, the expansion bus interface 184 may be an electronic overload CAN communication interface. The expansion bus interface 184 may enable communication between the gateway interface device 172 and any number of operator stations, such as operator station 200, any number of control stations, and/or any number of diagnostic stations. The operator station 200 may transmit one or more data signals for control of the solid-state circuit breaker 14. In certain embodiments, the operator station 200 may include a user interface for selecting a set of commands for operating the solid-state circuit breaker 14. The gateway interface device 172 may receive the data signals via the expansion bus interface 184 and the corresponding communication port 194. In certain embodiments, the controller 174 may translate the data signals received from the operator station 200 between a first format (e.g., CAN communication protocol) to a second format (e.g., CAN FD communication protocol). Additionally or alternatively, the controller 174 may translate data signals received from the solid-state circuit breaker 14 (e.g., an operational status of the solid-state circuit breaker) from the CAN FD format to the CAN format.

Keeping the foregoing in mind, FIG. 13 is a block diagram of a gateway interface device, such as the gateway interface device 172 of FIG. 11 , incorporating a digital signal communication interface including a digital OUT communication port 204 and a digital IN communication port 206. The gateway interface device 172 may include any number of communication interfaces, such as the Ethernet DLR interface 180, the subnet interface 182, an Ethernet Transmission Control Protocol (TCP) interface 208, the Expansion Bus interface 184, and the digital signal communication interface.

In certain embodiments, the subnet interface 182 may enable communication between the gateway interface device 172 and a pilot device 202. The pilot device 202 may be a pilot switch and/or a pilot light. A pilot device may control operation of another device and/or indicate an operational status of another device. A pilot light may provide a visual indication of an operational status. For example, the pilot light may indicate an energized status for the solid-state circuit breaker when the pilot light is illuminated, may indicate a de-energized status when the pilot light is off, an alarm or trip condition by a flashing the pilot light, and the like.

In some embodiments, the digital signal communication interface may enable communication between a local device and the gateway interface device 172 for control of the solid-state circuit breaker 14. The digital signal communication interface may use a 24V signal for communication of data signals between a local device and the gateway interface device 172. The controller 174 may receive commands to energize, de-energize (e.g., trip), determine and/or transmit an operational status of the solid-state circuit breaker 14, and the like via the digital signal communication interface. For example, a local device may transmit a data signal to the gateway interface device 172 via the digital IN communication port 206. The controller 274 may translate the data signal from a digital signal format to the CAN FD format and may transmit the translated data signal to the solid-state circuit breaker 14 via the solid-state circuit breaker interface 176 for operation of the solid-state circuit breaker 14.

Keeping the foregoing in mind, FIG. 14 illustrates a flow chart of a method 210 for determining device connections for a gateway interface device, such as the gateway interface device 172 of FIG. 11 , in accordance with an embodiment of the present disclosure. While the method 210 is described as being performed by the controller 174, it should be understood that the method 210 may be performed by any suitable device, such as a processor, that may control and/or communicate with components of a motor-feeder system protected by a solid-state circuit breaker. Furthermore, while the method 210 is described using steps in a specific sequence, it should be understood that the present disclosure contemplates that the described steps may be skipped or not performed altogether. In some embodiments, the method 210 may be implemented by executing instructions stored in a tangible, non-transitory, computer-readable medium using any suitable processing circuitry.

In the method 210, the controller 174 may receive a start up request (block 212). The start up request may be indicative of an interaction with a user interface of the gateway interface device 172. For example, a user may input a selection into the user interface and the start up request may be generated in response to the input. In certain embodiments, the start up request may correspond to an initialization of the gateway interface device 172. Initialization of the gateway interface device 172 may include turning on a power supply, such as the power supply 178 in FIG. 12 , and providing power to components of the gateway interface device 172.

The controller 174 may determine a set of communication interfaces available to the gateway interface device 172 (block 214). In some embodiments, the controller 174 may generate one or more data signals for transmission via the set of the communication interfaces. For example, the controller 174 may generate a set of data signals for transmission via the set of the communication interfaces based on a set of communication protocols that correspond to the set of the communication interfaces. A memory associated with the gateway interface device 172 may store the set of data signals as test signals for various communication interfaces. In addition, the memory may include a set of algorithms for translating various types of data signals into signals interpretable by each communication protocol of the set of communication protocols. The controller 174 may transmit the set of data signals via a set of communication interfaces and may receive one or more responses from devices receiving the respective data signal. In some embodiments, the responses may include data packets associated with a respective communication interface. For example, the controller 174 may detect that a first data packet is received via a first communication interface using a first communication protocol. As such, the controller 174 may determine that the first communication interface is available to the gateway interface device 172. The controller 174 may then identify the communication interfaces that available to the gateway interface device 172.

The controller 174 may also determine a set of devices associated with each communication interface of the set of communication interfaces (block 216). In some embodiments, the response may include one or more data packets associated with a device transmitting the one or more data packets. For example, the one or more data packets may include an identifier associated with the device. The controller 174 may receive the one or more data packets and may determine a device associated with the one or more data packets based on the identifier. As such, the controller 174 may associate the device with a communication interface through which the one or more data packets were received. In some embodiments, the controller 174 may associate the device based on a communication protocol associated with the one or more packets. For example, the controller 174 may determine that a solid-state circuit breaker is connected with a solid-state circuit breaker interface based on receiving data packets via a CAN FD communication protocol. In certain embodiments, the controller 174 may group devices according to a corresponding communication interface. For example, the controller 174 may group any number of solid-state circuit breakers communicatively coupled to the gateway interface device 172 via the solid-state circuit breaker interface, such that data received from these solid-state circuit breakers may be translated together by the controller 174, one or more commands may be sent to the group of solid-state circuit breakers to perform an operation, or the like.

Based on the set of connected devices, the controller 174 may generate a node list (block 218) for each communication interface. The node list may include any number of nodes, such that each node associated with a communication interface. For example, the controller 174 may identify a node associated with an Ethernet DLR interface and the node may include a set of devices communicatively coupled to the gateway interface device 172 via the Ethernet DLR interface. In certain embodiments, the node list may include separate nodes for each device communicatively coupled to the gateway interface device 172. For example, each node may be associated with a device communicatively coupled to the gateway interface device 172 and a corresponding communication interface associated with the device.

In certain embodiments, the controller 174 may transmit a subset of the node list to any number of devices communicatively coupled to the gateway interface device 172. In certain embodiments, the controller 174 may transmit the subset of the node list to a device based on a corresponding communication interface. For example, the controller 174 may determine that an operator station is communicatively coupled to the gateway interface device 172 via an expansion bus interface. As such, the controller 174 may transmit a subset of the node list associated with the expansion bus interface to the operator station. In certain embodiments, the subset of the node list may be a single node and may include each of the devices communicatively coupled to the gateway interface device 172 via the expansion bus interface. Additionally or alternatively, the subset of the node list may include a single node and the single node may correspond to the device receiving the transmitted node list.

The controller 174 may also create (block 220) a dynamic data table for mapping device data based on the node list and/or the determined set of connected devices. For example, the mapping may identify a communication interface associated with each device from the set of device connections. In certain embodiments, the dynamic data table may be stored in a shared memory of the gateway interface device 172. In some embodiments, the mapping may indicate a set of devices associated with each communication interface from the set of communication interfaces. In certain embodiments, the mapping may indicate a communication protocol associated with each device and/or with each communication interface.

The controller 174 may assign (block 222) data from each device on each interface based on a set of memory locations and the mapping. The controller 174 may determine a number of memory locations based on the set of communication interfaces and/or the set of device connections. For example, the number of memory locations may correspond to the set of communication interfaces and the controller 174 may assign each communication interface a separate memory location within a memory of the gateway interface device 172. In some embodiments, the number of memory locations may correspond to the set of connected devices, and the controller 174 may assign each device a separate memory location, such that data transmitted to or received or from a respective device may use a respective memory location. Additionally or alternatively, the controller 174 may assign one or more connected devices to one or more sublocations of each memory location associated with a communication interface. For example, the controller 174 may assign each solid-state circuit breaker a separate memory sublocation within a memory location associated with the solid-state circuit breaker interface.

The controller 174 may then transmit (block 224) a set of read requests to the set of connected devices. For example, the read request may request an operational status of each device. In certain embodiments, the read request may request a set of data associated with each device. For example, the set of data may include a device type, a device model, a set of operational parameters associated with the device, a communication protocol associated with the device, and so forth. In some embodiments, the read request may request an acknowledgement in response to receiving the read request.

In response to sending the read request, the controller 174 may receive (block 226) a set of data in response to at least read request of the set of read requests. The set of data may include an acknowledgement indicating receipt of the read request. In certain embodiments, the controller 174 may receive a set of data from each device communicatively coupled to the gateway interface device 172 in response to transmitting the set of read requests. The controller 174 may receive the set of data according to a communication protocol associated with the device based on the mapping. If no set of data is received from any device of the set of devices, the controller 174 may periodically transmit a new read request for a new set of data. Additionally or alternatively, the controller 174 may periodically send a new read request to update the previously received set of data.

In some embodiments, the controller 174 may authenticate the set of device connections based on the set of data. For example, the controller 174 may authenticate a device connection based on an acknowledgement in the set of data. As such, the controller 174 may ensure communication between the gateway interface device 172 and the device is available. The controller 174 may then store the set of data based on the mapping. For example, the controller 174 may determine a memory location associated with a communication interface corresponding to the set of data and may store the set of data in the memory location. In certain embodiments, the controller 174 may store the set of data within a memory location and/or memory sublocation associated with a device corresponding to the set of data. Additionally or alternatively, the controller 174 may update the set of data based on a new set of data received in response to a new transmitted read request.

After authenticating the set of device connections, the controller 174 may receive data from the set of devices (block 228). For example, the controller 174 may receive data indicative of an instruction to operate one or more solid-state circuit breakers, operational data associated with one or more solid-state circuit breakers, operational data associated with an electrical load coupled to a respective solid-state circuit breaker, and the like. In certain embodiments, the controller 174 may store data (230) within the dynamic data table based on the mapping. For example, the controller 174 may determine a memory location associated with a particular device connection and may store data received via the device connection in the associated memory location. In certain embodiments, the controller 174 may translate data received from the set of devices and may determine the data is indicative of an instruction for a second device connection for the gateway interface device 172. As such, the controller 174 may store the translated data in an associated memory location for the second device connection. In some embodiments, the controller 174 may transmit the translated data to the second device via the second device connection.

Since the controller is able to facilitate communication between any number of communication protocols, any number of devices (e.g., solid-state circuit breakers, operator stations, pilot devices) can be accessible and may receive and transmit communications regardless of interface. In this way, the controller 174 may control one or more solid-state circuit breakers to modify an operational status, protect devices coupled to a respective solid-state circuit breaker, and coordinate industrial systems in a more efficient manner without waiting for mechanical circuit breakers, which take longer to switch operating modes and allow for peak currents to change, which can harm devices and incapacitate industrial plant systems.

Keeping the foregoing in mind, FIG. 15 is a flowchart of a method 240 for communicating between connected devices and the solid-state circuit breaker of FIG. 1 using the gateway interface device of FIG. 11 , in accordance with an embodiment of the present disclosure. While the method 240 is described as being performed by the controller 174, it should be understood that the method 240 may be performed by any suitable device, such as a processor, that may control and/or communicate with components of a motor-feeder system protected by a solid-state circuit breaker 14. Furthermore, while the method 240 is described using steps in a specific sequence, it should be understood that the present disclosure contemplates that the described steps may be skipped or not performed altogether. In some embodiments, the method 240 may be implemented by executing instructions stored in a tangible, non-transitory, computer-readable medium using any suitable processing circuitry.

At block 242, the controller 174 may generate an instruction associated with a first device. In some embodiments, the controller 174 may receive the instruction from a second device via at least one communication interface of a set of communication interfaces of the gateway interface device 172. For example, the controller 174 may receive an instruction from the operator station 200 via the expansion bus interface 184 and the instruction may cause an operation (e.g., energize, de-energize, trip) to occur at the solid-state circuit breaker 14. As such, the instruction may be in a first format (CAN communication protocol). In some embodiments, the instruction may be associated with any number of devices communicatively coupled to the gateway interface device 172. For example, the instruction may be intended for any number of solid-state circuit breakers. In certain embodiments, the instruction may not be associated with any device communicatively coupled to the gateway interface device 172. As such, the gateway interface device 172 may generate and may transmit a data signal indicative of an error to the second device. For example, the data signal may cause an error code to display at a user interface of the second device and the error code may indicate no connected device can be found for the instruction.

In certain embodiments, the controller 174 may act as a pass-through device between the first device and the second device. For example, the controller 174 may receive the instruction from the second device (e.g., operation station 200) and may determine the instruction is intended to be passed through to the solid-state circuit breaker. The controller 174 may determine the instruction is associated with an operation to occur at the solid-state circuit breaker. For example, the controller 174 may determine the instruction causes the solid-state circuit breaker to adjust an operation.

After generating the instruction at block 242, the controller 174 may, at block 244, determine a communication protocol based on a communication interface associated with the first device. For example, the controller 174 may determine that the solid-state circuit breaker is communicatively coupled to the gateway interface device at the solid-state circuit breaker interface 176. As such, the controller 174 may determine that the solid-state circuit breaker utilizes a CAN FD communication protocol. In certain embodiments, the controller 174 may determine the instruction is associated with any number of devices and may determine any number of communication protocols based on corresponding communication interface for the devices.

At block 246, the controller 174 may translate the instruction based on the communication interface determined at block 244. For example, the controller 174 may translate an instruction to the CAN FD communication protocol when the instruction is intended for the solid-state circuit breaker. In some embodiments, the controller 174 may translate the instruction to any number of communication protocols (e.g., CAN FD, USB, Ethernet TCP) based on a set of devices associated with the instruction and the corresponding set of communication interfaces associated with the set of devices. The controller 174 may translate the instruction from the first format (e.g., CAN communication protocol) to a second format (e.g., CAN FD protocol) associated with the device to receive the instruction. At block 248, the controller 174 may transmit the translated instruction to the device associated with the instruction. For example, the controller 174 may use a corresponding communication interface associated with the device to transmit the translated instruction. As such, the device may receive the instruction and may carry out any steps or operation associated with the instruction.

As such, method 240 allows the controller 174 to communicate with any number of devices via any number of communication interfaces. The controller 174 may facilitate communication between one or more solid-state circuit breakers and a control device (e.g., operator station 200) that may instruct and may control operation of the one or more solid-state circuit breakers. For example, the controller 174 may translate instructions from a control device between a first communication protocol associated with the control device and a second communication protocol associated with one or more solid-state circuit breakers. The controller 174 may then transmit instructions to one or more solid-state circuit breakers. Likewise, the controller 174 may translate operational information received from one or more solid-state circuit breakers and may transmit the operational information to one or more control devices.

In some cases, the solid-state circuit breaker 14 may be disposed in an enclosure, such as the cabinet 130 in FIG. 8 . In this case, the gateway interface device 172 may receive an operational status corresponding to the solid-state circuit breaker 14, a lock (e.g., latch device 114), and/or a door (e.g., drawer door, hinged door in FIG. 10 ). In this way, the gateway interface device 172 may control operation of solid-state circuit breaker, the lock, and/or the door, such that access to and/or removal of the solid-state circuit breaker 14 may be permitted based on the one or more operational statuses. For example, prior to energizing the solid-state circuit breaker 14, the gateway interface device 172 may ensure that access to the solid-state circuit breaker is prevented by closing and/or locking a door of the enclosure. As such, the coordinated communications to various devices via the gateway interface device 172 may ensure that certain components are de-energized using the solid-state circuit breaker 14 before providing the components are accessible.

Keeping the foregoing in mind, FIG. 16 is a flowchart of a method 250 for operating an enclosure using the gateway interface device 172 of FIG. 11 prior to energizing the solid-state circuit breaker of FIG. 11 , in accordance with an embodiment of the present disclosure. While the method 250 is described as being performed by the controller 174, it should be understood that the method 250 may be performed by any suitable device, such as a processor, that may control and/or communicate with components of a motor-feeder system protected by a solid-state circuit breaker. Furthermore, while the method 250 is described using steps in a specific sequence, it should be understood that the present disclosure contemplates that the described steps may be skipped or not performed altogether. In some embodiments, the method 250 may be implemented by executing instructions stored in a tangible, non-transitory, computer-readable medium using any suitable processing circuitry.

Referring now to FIG. 16 , the controller 174 may receive an instruction to energize the solid-state circuit breaker 14. For example, the controller 174 may receive one or more data signals via any number of communication interfaces that request a change in an operation of one or more solid-state circuit breakers. The instruction may be generated by the controller 174 based on an input received from a user, based on a condition (e.g., measured value exceeds a threshold) being present, or the like. In any case, prior to implementing that instruction, the controller 174 may perform the method 250 to ensure that an enclosure protecting the solid-state circuit breaker 14 from access by other persons is secure before energizing the solid-state circuit breaker 14.

With this in mind, at block 252, the controller 174 determine an operational status of the solid-state circuit breaker 14. As such, the controller 174 may send a request to the solid-state circuit breaker 14 to determine an operational status of the solid-state circuit breaker. For example, the controller 174 may send a data signal indicative of a request for the operational status via a CAN FD communication interface. The controller 174 may then receive, translate, and/or may determine the operational status of the solid-state circuit breaker based on a response received regarding the transmitted data signal. The operational status may indicate whether the solid-state circuit breaker 14 is in an energized or a de-energized state.

At block 254, the controller 174 may determine a door position status. For example, the controller 174 may receive a data signal from a door sensor or some other sensor disposed on the enclosure. The data signal received from the sensor may be indicative of the door position status (e.g., open, closed) for a door that provides access to internal components, such as the solid-state circuit breaker 14, via a door. In some embodiments, the door position should be closed prior to energization of the solid-state circuit breaker 14 to ensure access and/or removal of the solid-state circuit breaker is prevented.

If the door position status is open, the controller 174 may proceed to block 262 and transmit a data signal to a user interface or a display that may be disposed on the respective door and/or enclosure. The data signal may be representative of a visualization, indication, or message indicating that the door to the enclosure is open and should be closed before energizing the solid-state circuit breaker 14. Additionally or alternatively, the controller 174 may send a command signal to an actuator coupled to the door that may cause the door to automatically close.

After transmitting the instruction to the user interface or the actuator, the controller 174 may, at block 264, transmit a second instruction to the user interface to provide instructions regarding an operation of a lock used to secure access to the solid-state circuit breaker 14. For example, the second instruction may cause an indication to appear on the user interface or display described above, such that they provide instructions for securing (e.g., locking) access to the solid-state circuit breaker 14. The indication may be viewed by an operator of the enclosure and the operator may lock the door in response to the indication. Additionally or alternatively, the instruction may be transmitted to an actuator associated with the lock to cause the lock to automatically move to the locked position in response to receiving the instruction.

Referring back to block 256, if the door position status corresponds to a closed door, the controller 174 may proceed to block 258 and determine a lock position status of the lock associated with the door. That is, the controller 174 may receive a data signal from the enclosure indicative of the lock position status (e.g., locked, unlocked). At block 260, if the controller 174 determines that the lock position status corresponds to an unlocked state, the controller 174 may proceed to block 264 and transmit a second instruction associated with the operation of the lock, as described above. If, however, at block 260, the lock position status is locked, the controller 174 may transmit an instruction to the solid-state circuit breaker 14 to cause the solid-state circuit breaker 14 to energize or close. That is, if the desired operational states for energizing the solid-state circuit breaker 14 are present, the controller 174 may proceed to operate the solid-state circuit breaker. As mentioned above, the controller 174 may transmit the instruction to the solid-state circuit breaker 14 via a CAN FD communication interface and may close in response to receiving the instruction. As such, the controller 174 may determine and may operate the solid-state circuit breaker based on the operational status of the door and/or the lock. As a result, the controller 174 may ensure the correct operational status of the solid-state circuit breaker 14, the door, and/or the lock before energization of the solid-state circuit breaker 14.

In certain instances, the controller 174 may assist in preventing access to the solid-state circuit breaker while the solid-state circuit breaker is in an energized state. The controller 174 may monitor the operational status of an enclosure housing the solid-state circuit breaker to ensure the door of the enclosure stays closed and/or the lock of the enclosure stays locked while the solid-state circuit breaker is in the energized state. The controller 174 may also operate the solid-state circuit breaker in response to receiving an indication that the door has opened and/or the lock has disengaged (e.g., unlocked). For example, the controller 174 may generate and may transmit an instruction to de-energize (e.g., trip) the solid-state circuit breaker in response to receiving the indication.

Keeping the foregoing in mind, FIG. 17 is a flow chart of a method 290 for operating the solid-state circuit breaker 14 of FIG. 1 using the gateway interface device of FIG. 11 in response to receiving a request to open the solid-state circuit breaker, in accordance with an embodiment of the present disclosure. While the method 290 is described as being performed by the controller 174, it should be understood that the method 290 may be performed by any suitable device, such as a processor, that may control and/or communicate with components of a motor-feeder system 10 protected by a solid-state circuit breaker 14. Furthermore, while the method 290 is described using steps in a specific sequence, it should be understood that the present disclosure contemplates that the described steps may be skipped or not performed altogether. In some embodiments, the method 290 may be implemented by executing instructions stored in a tangible, non-transitory, computer-readable medium using any suitable processing circuitry.

In certain embodiments, the controller 174 may receive a request indicative of an operation to be performed at one or more solid-state circuit breakers. For example, at block 292, the controller 174 may receive a request to open one or more solid-state circuit breakers 14. In some embodiments, the controller 174 may receive a data signal representative of an instruction from a control device via a communication interface, as described above. In certain embodiments, the controller 174 may translate the instruction from a first communication protocol associated with the control device to a second communication protocol associated with one or more solid-state circuit breakers, such that the translated instruction is capable of operating the one or more solid-state circuit breakers. At block 294, the controller 174 may transmit the instruction to one or more solid-state circuit breakers, such that the one or more solid-state circuit breakers are opened or tripped in response to receiving the instruction.

In some embodiments, the controller 174 may transmit a data signal or instruction (block 296) to a user interface or a display that may be disposed on a respective door and/or enclosure of a solid-state circuit breaker. In certain embodiments, the data signal or instruction may be associated with the operation of a respective door and/or enclosure of a solid-state circuit breaker and based on the solid-state circuit breaker having a de-energized (e.g., open) operational status. As such, the controller 174 may transmit the data signal or instruction to any number of doors and/or enclosures for any number of solid-state circuit breakers. The data signal may be representative of a visualization, indication, or message indicating that the door to the enclosure can be opened because the solid-state circuit breaker is de-energized. Additionally or alternatively, the controller 174 may send a command signal to an actuator coupled to the door that may cause the door to automatically open.

After transmitting the instruction to the user interface or the actuator, the controller 174 may, at block 298, transmit a second instruction to the user interface to provide instructions regarding an operation of a lock used to secure access to the solid-state circuit breaker 14. For example, the second instruction may cause an indication to appear on the user interface or display described above, such that they provide instructions for allowing (e.g., unlocking) access to the solid-state circuit breaker 14. In certain embodiments, the controller 174 may transmit the second instruction to any number of user interfaces associated with any number of solid-state circuit breakers. The indication may be viewed by an operator of the enclosure and the operator may unlock the door in response to the indication. Additionally or alternatively, the instruction may be transmitted to an actuator associated with the lock to cause the lock to automatically move to the unlocked position in response to receiving the instruction.

The controller 174 may generate and may store a log associated with the instructions (block 300). For example, the log may include a timestamp associated with the instruction, one or more door position statuses, one or more lock position statuses, and/or a user associated with the instruction. The controller 174 may store the log in a memory of the gateway interface device 172. Additionally or alternatively, the controller 174 may transmit the log to any number of devices via any number of communication interfaces associated with the gateway interface device 172.

During peak periods of power demand, certain loads may be prioritized over other loads in an industrial plant system to prevent failure of the entire system. For example, refrigeration, heating, air conditioning, and similar components may be given higher priority over in a load shedding program. A gateway interface device may assist in setting up and controlling a load shedding program based on the power demand and may operate any number of solid-state circuit breakers 14 to ensure the power demand does not exceed the available power supply.

Keeping the foregoing in mind, FIG. 18 is a flowchart of a method 310 for controlling operation of a set of circuit breakers using the gateway interface device 172 of FIG. 11 , in accordance with an embodiment of the present disclosure. While the method 310 is described as being performed by the controller 174, it should be understood that the method 310 may be performed by any suitable device, such as a processor, that may control and/or communicate with components of a motor-feeder system 10 protected by a solid-state circuit breaker 14. Furthermore, while the method 310 is described using steps in a specific sequence, it should be understood that the present disclosure contemplates that the described steps may be skipped or not performed altogether. In some embodiments, the method 310 may be implemented by executing instructions stored in a tangible, non-transitory, computer-readable medium using any suitable processing circuitry.

At block 312, the controller 174 may receive an input indicative of an assignment of a set of solid-state circuit breakers 14 to be used for a load shedding program. As such, the controller 174 may assign any number of solid-state circuit breakers 14 for the load shedding program based on user input. In addition, the controller 174 may automatically identify solid-state circuit breakers 14 to use for load shedding. For example, the controller 174 may assign the set of solid-state circuit breakers 14 based on a type of device (e.g., power generating, power consuming) associated with a corresponding solid-state circuit breaker 14. Additionally or alternatively, the controller 174 may assign the set of solid-state circuit breakers based on an operational status of each solid-state circuit breaker 14. For example, the controller 174 may determine any number of solid-state circuit breakers that are in an energized state (e.g., closed). In certain embodiments, the controller 174 may assign each energized solid-state circuit breaker to the set of solid-state circuit breakers for the load shedding program. Additionally or alternatively, the controller 174 may update the set of solid-state circuit breakers with additional solid-state circuit breakers which have been shifted to the energized state.

At block 314, the controller 174 may determine a priority order for the set of solid-state circuit breakers. In certain embodiments, the priority order may include any number of levels. For example, each level may include a subset of the set of solid-state circuit breakers. Each level may be ranked according to a priority of the level for shedding loads. For example, levels with lower priority may be turned off (e.g., de-energized, tripped) before levels with higher priority. In some embodiments, the controller 174 may determine the priority order based on a set of operational factors, such as a device type associated with a corresponding solid-state circuit breaker, a model of device associated with the corresponding solid-state circuit breaker 14, a load associated with the corresponding solid-state circuit breaker, the overall power demand associated with the set of solid-state circuit breakers 14, the available power capacity, and the like.

Additionally or alternatively, the priority order may include a ranking of each solid-state circuit breaker 14 in the set of solid-state circuit breakers. The ranking may include a highest priority value, a lowest priority value, and any number of priority values therebetween. In some embodiments, the controller 174 may assign each solid-state circuit breaker in the set of solid-state circuit breakers a different priority value. In certain embodiments, the controller 174 may assign each solid-state circuit breaker 14 a different priority value in each level. For example, a solid-state circuit breaker 14 may have a priority level of two and a priority value of five. As such, the solid-state circuit breaker 14 may have a second highest level of priority and a fifth highest value of priority within the second level. The priority levels may be defined by a user or may be determined based on the type of device connected to the respective solid-state circuit breaker 14. That is, core functions, such as drives, motors, mixers, conveyors, another other equipment directly related to production may have a higher level of priority as compared to equipment that may be related to monitoring operations or performing non-core operations.

At block 316, the controller 174 may determine whether load shedding is necessary. For example, the controller 174 may monitor the overall power demand associated with the set of solid-state circuit breakers 14 and may compare the power demand with an available power capacity. In certain embodiments, the controller 174 may determine whether the overall power demand is within a threshold percentage of the available power capacity (e.g., sixty percent, eighty percent, ninety percent, and so forth). As such, the controller 174 may determine load shedding is necessary when the overall power demand is within the threshold percentage of the available power capacity. Additionally or alternatively, the controller 174 may determine load shedding is necessary based on a set of factors. The set of factors may include, the overall power demand, an overall power threshold, a device power threshold, the available power capacity, a time of day, a day of the week, a date, a number of solid-state circuit breakers in the set of solid-state circuit breakers, a set of device types of a set of devices associated with the set of solid-state circuit breakers, and the like.

In some embodiments, a historical set of factors may include a historical power demand and/or a historical power capacity. For example, the controller 174 may generate and may store a log in response to previous load shedding incidents. The log may include the historical set of factors, such as a set of solid-state circuit breakers associated with the load shedding incident, a time, a date, a day of the week, a number of solid-state circuit breakers, and so forth. In certain embodiments, the controller 174 may compare a current set of factors with a historical set of factors and determine whether load shedding is necessary based on the comparison. In some embodiments, the controller 174 may weight each factor. For example, the overall power demand and/or available power capacity may be weighted more heavily than a time.

Based on the factors described above, the controller 174 may determine whether load shedding is necessary at block 316. If the controller 174 determines that the load shedding is not necessary, the controller 174 may return to block 316 and continue monitoring the set of factors to periodically determine whether load shedding is necessary.

If the controller 174 determines that the load shedding is necessary, the controller 174 may proceed to block 318 and receive data related to a set of operational parameters associated with devices that correspond to the set of solid-state circuit breakers 14 designated for load shedding. For example, the controller 174 receive data via the gateway interface device 172 described above using the appropriate communication protocol and interface. By way of example, the controller 174 may receive data related to a power demand for each device connected to a respective solid-state circuit breaker 14 and determine an overall power demand for a set of devices that correspond to the set of solid-state circuit breakers 14.

At block 320, the controller 174 may select a subset of the solid-state circuit breakers 14 based on the priority order. For example, the controller 174 may select the solid-state circuit breakers 14 in one or more levels of the priority order. In some embodiments, the controller 174 may select a percentage (e.g., five percent, ten percent, twenty percent) of the set of solid-state circuit breakers according to the priority order. For example, the controller may select a percentage of the set of solid-state circuit breakers having the lowest priority according to the priority order. In certain embodiments, the controller 174 may select one or more solid-state circuit breakers from one or more priority levels according to the priority order. For example, the controller 174 may select a subset of solid-state circuit breakers having the lowest priority in each priority level. In some embodiments, the subset of solid-state circuit breakers 14 may be selected to accommodate the desired load associated with determining whether the load shedding was necessary at block 316.

At block 322, the controller 174 may generate and transmit an instruction to the subset of solid-state circuit breakers 14 selected at block 320. The instruction may cause the subset of solid-state circuit breakers to trip, de-energize, or open in response to receiving the instruction. As a result, an overall power demand to the devices connected to the subset of solid-state circuit breakers 14 may be reduced due to the open circuit state of the subset of solid-state circuit breakers. The controller 174 may then return to block 318 and receive an update to the operational status associated with the one or more solid-state circuit breakers. Based on the updated operational statuses, the controller 174 may remove the de-energized solid-state circuit breakers 14 from the set of solid-state circuit breakers. The controller 174 may then continue to select additional solid-state circuit breakers 14 to open until the load shedding goals are achieved.

With the foregoing in mind, FIG. 19 is a block diagram of a gateway interface device. such as the gateway interface device 172 of FIG. 11 , incorporating a Universal Serial Bus (USB) interface 340, in accordance with an embodiment of the present disclosure. In certain embodiments, the gateway interface device 172 may include any number of communication interfaces, such as the Ethernet DLR interface 180 and the USB interface 340. The gateway interface device 172 may include a communication port 342 associated with the USB interface 340. The USB interface 340 may permit communication with any number of devices via data packets transferred between the devices and the gateway interface device 172.

Technical effects of the present disclosure include techniques for protecting an electrical load from abnormal operation, transients, overvoltage, or the like, that may affect power supplied to the electrical load. A solid-state circuit breaker may be included upstream from an electrical load. The solid-state circuit breaker may be manufactured to not use mechanical switching to electrically isolate its output from its input. Reducing or eliminating use of mechanical switching may reduce a likelihood of arc flash and/or reduce a severity of exposed incident energy if an arc flash were to occur. Furthermore, a control system may communicatively couple to the solid-state circuit breaker and may receive operational indications and/or statuses from the solid-state circuit breaker. The control system may update a model (e.g., a model rendered on a display) using information received from the solid-state circuit breaker in real-time. This model may be used to support real-time updates of a motor control center (MCC) model and electrical statuses of respective solid-state circuit breakers, providing for an improved monitoring and deployment solution of MCC monitoring technologies.

While only certain features of the presently disclosed embodiments have been illustrated and described herein, many modifications and changes will occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the embodiments described herein. 

1. A system, comprising: a solid-state circuit breaker configured to couple between a power supply and an electrical load; and a gateway interface device communicatively coupled to a controller of the solid-state circuit breaker and comprising a plurality of communication interfaces, wherein each of the plurality of communication interfaces is configured to communicate using a different communication protocol, and wherein the controller is configured to perform operations comprising: determining a connection status of at least one communication interface of the plurality of communication interfaces based on a set of data signals received via the at least one communication interface; determining a set of devices connected to the at least one communication interface based on the set of data signals received via the at least one communication interface; creating a data table configured to map data received from each device of the set of devices into a shared memory; and storing data received from the set of devices in the shared memory based on the data table.
 2. The system of claim 1, wherein the at least one communication interface comprises an Ethernet internet protocol (IP) communication interface, an Ethernet subnet communication interface, an expansion bus communication interface, a Universal Serial Bus (USB) communication interface, a Controller Area Network Flexible Data Rate (CAN FD) communication interface, or any combination thereof.
 3. The system of claim 1, wherein the controller is configured to perform operations comprising: receiving, from the solid-state circuit breaker, a signal via a first communication interface of the plurality of communication interfaces, wherein the signal is indicative of an operational state of the solid-state circuit breaker; and translating the signal from a first communication protocol associated with the first communication interface to a second communication protocol associated with the at least one communication interface of the plurality of communication interfaces.
 4. The system of claim 3, wherein the controller is configured to perform operations comprising transmitting the translated signal to a first device of the set of devices via the at least one communication interface.
 5. The system of claim 1, wherein the controller is configured to perform operations comprising causing the solid-state circuit breaker to adjust an operational state.
 6. The system of claim 5, wherein the operational state comprises an open circuit or a closed circuit.
 7. The system of claim 1, wherein the controller is configured to perform operations comprising: receiving, from the solid-state circuit breaker, a signal indicative of an operational state associated with the solid-state circuit breaker; and transmitting the signal to a first device of the set of devices, wherein the signal is configured to cause the first device to provide an indication associated with the operational state of the solid-state circuit breaker.
 8. The system of claim 1, wherein the controller is configured to perform operations comprising: receiving, from a first device of the set of devices, a signal via the at least one communication interface; translating the signal from a first communication protocol to a second communication protocol; and transmitting the translated signal to the solid-state circuit breaker via a second communication interface.
 9. A method, comprising: receiving, by a processor, a signal indicative of adjusting an operational status of a solid-state circuit breaker disposed in an enclosure; in response to receiving the signal: determining, by the processor, a door position status for a door of the enclosure; and adjusting, by the processor, the operational status of the solid-state circuit breaker based on the door position status and the signal.
 10. The method of claim 9, comprising determining, by the processor, a lock position status associated with a lock of the enclosure, wherein the lock position status is indicative of the lock being engaged.
 11. The method of claim 9, wherein adjusting the operational status of the solid-state circuit breaker comprises coupling a voltage to an electrical load via the solid-state circuit breaker.
 12. The method of claim 9, wherein the door position status is indicative of the door being closed.
 13. The method of claim 9, comprising generating a log associated with adjusting the operational status of the solid-state circuit breaker.
 14. The method of claim 13, wherein the log includes a timestamp, the door position status, a user associated with the solid-state circuit breaker, or any combination thereof.
 15. A gateway interface device, comprising: a plurality of communication interfaces, each communication interface configured to communicatively couple to a respective solid-state circuit breaker of a set of solid-state circuit breakers, each solid-state circuit breaker configured to couple between a respective power supply and a respective electrical load; and a controller configured to perform operations comprising: determining a total electrical load associated with the set of solid-state circuit breakers exceeds a threshold; and causing a subset of the set of solid-state circuit breakers to open in response to the total electrical load exceeding the threshold.
 16. The gateway interface device of claim 15, wherein a first communication interface of the plurality of communication interfaces is associated with a first communication protocol and a second communication interface of the plurality of communication interfaces is associated with a second communication protocol.
 17. The gateway interface device of claim 15, wherein the controller is configured to perform operations comprising receiving a set of operational factors comprising a device type associated with the respective electrical load, a first value indicative of the respective electrical load, a second value indicative of the respective power supply, or any combination thereof.
 18. The gateway interface device of claim 15, wherein the controller is configured to perform the operations comprising: determining an adjustment of an operational state of a first solid-state circuit breaker of the set of solid-state circuit breakers; and assigning the first solid-state circuit breaker to the subset of solid-state circuit breakers.
 19. The gateway interface device of claim 15, wherein the controller is configured to perform the operations comprising generating a log based on the total electrical load exceeding the threshold, wherein the log comprises an indication of the subset of the solid-state circuit breakers, a number of solid-state circuit breakers in the subset of the solid-state circuit breakers, a time associated with the total electrical load exceeding the threshold, or any combination thereof.
 20. The gateway interface device of claim 15, wherein the controller is configured to perform the operations comprising: determine a respective operational state for each solid-state circuit breaker of the set of solid-state circuit breakers; and based on the respective operational state being an energized state, assigning one or more of the set of solid-state circuit breakers to the subset of solid-state circuit breakers. 